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

Zeal crashes on start and quit #605

Closed
noamelf opened this issue Oct 1, 2016 · 13 comments
Closed

Zeal crashes on start and quit #605

noamelf opened this issue Oct 1, 2016 · 13 comments

Comments

@noamelf
Copy link

noamelf commented Oct 1, 2016

Hi Zeal looks great, but unfortunately, it crashes randomly on boot and quit.
See core dump.

I'm using Arch linux and installing Zeal with this AUR package (zeal-git 0.3.0.1.g0e6d4ff-1).

@trollixx
Copy link
Member

trollixx commented Oct 1, 2016

Thanks for the report. The crash on quit may be the same as #595. Not sure about random crash on start.

I've updated the package to build with debug info enabled. Please update Zeal, and post a new stack trace. It should be more helpful, thanks!

@noamelf
Copy link
Author

noamelf commented Oct 2, 2016

Here is the new core dump after reinstalling the package. I noticed there several different ones, so I'm attaching a few:

  • On close: 1, 2
  • On open: 1

@trollixx
Copy link
Member

trollixx commented Oct 2, 2016

zeal[0x43a43b]
zeal[0x4303f1]
zeal[0x42c76a]
zeal[0x4217eb]
zeal[0x41f0dc]

It didn't work. :( No symbol information. You've got zeal-git 0.3.0.1.g0e6d4ff-2 from AUR, right?

I don't know why, maybe something overrides the build configuration, or I used the wrong option. I'll update AUR once I figure out what's wrong.

@trollixx
Copy link
Member

trollixx commented Oct 2, 2016

Another update, hopefully with meaningful traces this time. Please update, and see if stack traces will have references to the code.

@noamelf
Copy link
Author

noamelf commented Oct 3, 2016

This is what I get after the update:
https://gist.github.com/noamelf/be6a6bf025b864cd52dee80ce2d52c08

@trollixx
Copy link
Member

trollixx commented Oct 3, 2016 via email

@cmalard
Copy link

cmalard commented Oct 3, 2016

Hi, same on Ubuntu with this error : zeal crashed with SIGSEGV in QCoreApplicationPrivate::sendPostedEvents()

@the-james-burton
Copy link

the-james-burton commented Oct 5, 2016

I concur. I have had the following zeal crash errors on Linux Mint 17.3 (based on ubuntu 14.04), installed via the ppa (0.3.0)...

*** Error in 'zeal': double free or corruption (!prev): 0x0000000000fad0c0 ***

and

QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES" 
QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES" 
QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES" 
QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES" 

I also see the 'another instance' error quite a lot. Note that it doesn't always fail. Once running, it will work for a while (often days with standbys in between) before crashing.

Previous release 0.2.1 was flawless. Sadly, I can't now find the 0.2.1 version anywhere, either via PPA or a working .deb file, so I can't downgrade (not without building it, I guess). Is it possible to provide a 0.2.1 version in the ppa until you have a fix?

@ronjouch
Copy link

ronjouch commented Oct 6, 2016

Zeal 0.3.0 also segfaults for me under Ubuntu 16.04.1LTS: [1] 20295 segmentation fault zeal.

Unfortunately I am unable to provide more traceback / debug info, as Zeal doesn't crash when built from source from QtCreator (Qt 5.7.0). Feel free to ask for more info.

@thuandt
Copy link

thuandt commented Oct 6, 2016

@ronjouch I have same problem like you in my laptop. Old one version is working fine

@dakira
Copy link

dakira commented Oct 7, 2016

Same here. Zeal 0.3.0 segfaults on exit. On every start I get a message that Zeal might still be running (which it's not). Couldn't find any crashlogs and only get a segfault message in the terminal.

@trollixx
Copy link
Member

trollixx commented Oct 8, 2016

Closing as a duplicate of #595. A fix is coming.

@lock
Copy link

lock bot commented Sep 16, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for a related request.

@lock lock bot locked and limited conversation to collaborators Sep 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

7 participants