Error Message on start and crash on exit #595
Comments
|
Could you build Zeal in the debug mode to get a meaningful backtrace? Just run The warning is about a local socket file left from the crashed instance. When you click |
|
I compiled it again with debug, but the output is pretty much the same. here is the compile output: |
|
Thanks for trying. The backtrace should have had references to the actual
lines of code. If it's the same (addresses only), then the only way would
be to run Zeal in a debugger. Could you do that? Dealing with gdb directly
is not the most pleasant experience, but it's very easy to do via Qt
Creator.
|
|
I pulled to commit bdaba34 I went to the GDB way. If it won't be enough I will install QT Creator. On later invocations this error disappears but for each exit there is segmenation fault. GDB stacktrace: |
|
I don't see anything specific :( Looks like If you know an older revision, when the problem didn't occur, Thank you for spending time on debugging this, I really appreciate that. |
|
Sorry it took time. I used Do you have any idea? This is a heavy commit. |
|
Thanks! This is the worst commit to cause a problem. Have you tried a completely clean build? If you build inside source tree, just run |
|
And another thing to try would be commenting out lines in MainWindow's
destructor. I may be deleting something in a wrong order.
|
|
I was able to reproduce the crash on my Ubuntu 14.04 VM, didn't have time to investigate the actual cause. |
|
Thanks! |
|
So, it's something Ubuntu related, we just don't know what exactly yet. And according to your findings 1c068d4 introduced that somehow... |
|
Hello, This issue also appears for me on the following machine:
I can confirm that a clean build before commit 1c068d4 clears all problems. Building version number 0.3.0 manually or through the AUR yielded the same results (crash on close). I quickly tried to check things out through GDB and got very similar results. So it might not be related to Ubuntu specifically. |
|
@Farenjihn thanks for the information. I have exactly same setup, but no crash. Since we know the exact change, should be relatively easy to hunt the problem down, and release a fix. |
trollixx
changed the title
|
Nice improvement in this version, but I got similar issue on For the moment I'm downgrading to |
|
Confirming, I have the same error. Crashing after exit on fresh install. After docset downloading - crashed right after start. OS: Arch Linux x86_64 |
Missing USE_APPINDICATOR in libs/core/ was causing the MainWindow class declaration to be truncated, thus causing memory corruption when later used with the full definition in libs/ui/.
|
I still have this problem. When I execute command in shell: You can see it cause |
|
@stardiviner Are you sure you built from the |
|
I tried the lates |
|
@stardiviner Oh, I didn't realise it crashes even for |
|
I execute command I don't know how to gdb on |
You need to pass Now when you get the SIGSEGV, type: to get a traceback. |
|
|
This maybe caused by KDE's |
|
Looks like https://bugreports.qt.io/browse/QTBUG-52988 |
|
For me the hotfix/0.3.1 solved the issue and --version also works as expected. |
|
@trollixx could you publish the |
|
I'm waiting for |
|
PPA has been updated to v0.3.1. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related requests. |
Hi,
I am using the latest build (commit a4fac24 from 15/9/2016).
I am on Ubuntu 16.04.
Zeal crashes on exit with the error below. The issue wasn't with the previous build dated several months before.
It seams that it causes also an error on start:
"Another application instance can be still running, or has crashed.
Make sure to start Zeal only once."
pressing Retry helps but the error is for each start of the application.
The error on exit:
The text was updated successfully, but these errors were encountered: