Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release mode runtime error #141

Open
sajadblog opened this issue Oct 16, 2024 · 3 comments
Open

Release mode runtime error #141

sajadblog opened this issue Oct 16, 2024 · 3 comments
Assignees

Comments

@sajadblog
Copy link
Contributor

Hi,

First of all, thank you for your tremendous effort in developing an excellent plotting tool. I’ve been using version 4.0.3 in my application, and it worked flawlessly in both release and debug modes.

Last week, I switched to the latest version on the main branch to take advantage of the MultiAxis graph and ColoredBar chart. While everything compiles and executes correctly in debug mode, I’m encountering a runtime error in release mode. The error seems to originate from within the Qt core library. It’s intermittent—sometimes the application runs fine, and other times, it fails at startup.

It seems like this issue might be related to some initialization that’s occasionally missing, as the error only occurs during startup. Once the application is running, everything works as expected.

I’ve attached two images related to the error. In most cases, one of the errors in the images occurs, though on rare occasions, it runs normally.

There is only one thread in the application.

Error1
Error2

@jkriege2 jkriege2 self-assigned this Oct 18, 2024
@jkriege2
Copy link
Owner

Hmmm ... hard to say ... I played around a bit with adress-sanitizer (the MSVC flavour), but couldn't find any issues ... other than that I never encountered such problems ...

Is your application very complex? Could there be any other source of heap corruption?

@jkriege2
Copy link
Owner

Could you use adress sanitizer on your application?

@sajadblog
Copy link
Contributor Author

Yes, it's really hard to pinpoint the issue. I tried ASan, and while there were no errors during compilation, it consistently shows this exception at runtime.

If I am the only one facing this issue, I’d suspect something unique to my application. However, since this is the only third-party library where the problem occurs, I’d greatly appreciate it if you could let me know if you have any suspicions about the cause.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants