Closed nouwaarom closed 4 years ago
Thanks for reporting. How long would you say it takes on average for a segfault to occur from the moment you start the program and load your document? I have not encountered this problem while developing this release, but given the severity of the problem, I will replicate your platform and investigate further.
Did you compile 0.8.0 yourself? If so, did you use the tarball/zip that is available on the 0.8.0 release as source? Does the GTK warning from your gdb log always show up when it crashes for you?
It really varies, sometimes I can work for ten hours at an end without this crash and sometimes it happens within half an hour. I think it occurs more often when I haven't saved the document for some time.
I compiled it myself, I built it from master.
Do you want me to test on the 0.8.0
tag?
Yes this gtk warning always shows up. If I do not run gummi in gdb it gets logged to the systemd journal and I see the error in journalctl.
No need - I reproduced and identified the issue. Little busy this weekend, but fix incoming asap.
During the migration to GTK3 I removed the initialization for a deprecated method of safely running gtk+ calls within a gdk thread without actually replacing all the instances of said method. My bad. Patch 48e4e59bb03e617dc98813b86f44e0c889422362 re-adds the initialization code to Gummi.
I ran a program that simulates user input into Gummi on a number of virtual machines and can reliably crash 0.8.0 within an hour of input. I can also reliably not have Gummi crash after several hours of constant input when this patch is applied.
Thanks very much for reporting this issue, 0.8.1 incoming now.
At random moments I get a segfault.
To Reproduce
System:
Other I used
gdb
to capture a stracktrace.