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

[OpenBSD] Crash upon exit #157

Open
vext01 opened this issue Sep 3, 2016 · 10 comments
Open

[OpenBSD] Crash upon exit #157

vext01 opened this issue Sep 3, 2016 · 10 comments

Comments

@vext01
Copy link

vext01 commented Sep 3, 2016

I can semi-reliably reproduce the following crash:

  • start qsyncthingtray
  • click icon to open webview
  • right click icon
  • quit

seg fault.

Building with symbols sadly does not help, suggesting that the crash is in QT itself.

Perhaps you are not tearing down the QT webview properly?

@vext01
Copy link
Author

vext01 commented Sep 3, 2016

(OpenBSD-current)

@mulander
Copy link

mulander commented Sep 3, 2016

Confirmed same issue on amd64 current. Sitting next to @vext01. Closing the webview before hand or not opening at all doesn't result in the segfault.

@sieren
Copy link
Owner

sieren commented Sep 4, 2016

Thanks, I assume this is built with WebKit and not WebEngine?
Any chance supplying me with a stacktrace?

@vext01
Copy link
Author

vext01 commented Sep 4, 2016

I'd need to build qt with symbols. Not one frame has a name in the trace currently.

@sieren
Copy link
Owner

sieren commented Sep 4, 2016

Could not reproduce this on Debian. Presumably it's BSD specific, a backtrace would really be helpful to determine whether it's a Qt issue or a QST one.

@sieren sieren changed the title Crash upon exit [OpenBSD] Crash upon exit Sep 4, 2016
@vext01
Copy link
Author

vext01 commented Sep 4, 2016

Ok. Ill build qt5 with symbols at some point.

Btw, how much memory does building qst take of your system. Im finding it
uses 1.6GB using gcc 4.9.4!

On 4 Sep 2016 11:34, "Matt Sieren" notifications@github.com wrote:

Could not reproduce this on Debian. Presumably it's BSD specific, a
backtrace would really be helpful to determine whether it's a Qt issue or a
QST one.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#157 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAk7G0soq8u6cafjXeX7JGNrNu97LKbfks5qmp7CgaJpZM4J0aRa
.

@sieren
Copy link
Owner

sieren commented Sep 4, 2016

I havent benchmarked that yet, but ran into problems on AppVeyor once with MSVC.
The immense memory usage is due to the QRC files (see Google search)

@vext01
Copy link
Author

vext01 commented Sep 8, 2016

The compile time memory consumption is the only thing preventing me importing qst into the OpenBSD ports tree :(

@sieren
Copy link
Owner

sieren commented Sep 11, 2016

Opened a separate issue for this

@sieren
Copy link
Owner

sieren commented Nov 23, 2016

On that note, is the crash on exit bug still an issue on OpenBSD? I assume it's related to the 200% reports.

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

No branches or pull requests

3 participants