QSyncthingTray
QSyncthingTray copied to clipboard
sieren
[OpenBSD] Crash upon exit
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?
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.
Thanks, I assume this is built with WebKit and not WebEngine? Any chance supplying me with a stacktrace?
I'd need to build qt with symbols. Not one frame has a name in the trace currently.
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.
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" [email protected] 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 https://github.com/sieren/QSyncthingTray/issues/157#issuecomment-244595372, or mute the thread https://github.com/notifications/unsubscribe-auth/AAk7G0soq8u6cafjXeX7JGNrNu97LKbfks5qmp7CgaJpZM4J0aRa .
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)
The compile time memory consumption is the only thing preventing me importing qst into the OpenBSD ports tree :(
On that note, is the crash on exit bug still an issue on OpenBSD? I assume it's related to the 200% reports.