GNOME Bugzilla – Bug 610051
Crash when using GktHtml whenever a report is opened
Last modified: 2018-06-29 22:35:04 UTC
Created attachment 153880 [details] Screenshot of error While trying to open a report, GnuCash crashes with an error message saying "gnucash-bin.exe has stopped working." The program then closes. This bug seems to be on all reports. After the first crash, everytime GnuCash is opened, the following error message is displayed "GnuCash could not obtain the lock for <filename>" The ledger, customer/vendor, and similar systems do not seem to have a problem, only reports. Tested system: Dell XPS410 Windows Vista Home Premium Intel dual-core 2.16GHz 4Gb Ram
Created attachment 153907 [details] Backtrace on report crash Confirmed on Windows XP as well. I have attached a backtrace. It seems that switching back to gtkhtml on windows requires more then disabling webkit and adding a configure option.
*** Bug 610038 has been marked as a duplicate of this bug. ***
The change that caused this crash has been reverted. By tomorrow, an new release should be available that no longer crashes on reports. By the way, regarding your information: > After the first crash, everytime GnuCash is opened, > the following error message is displayed > "GnuCash could not obtain the lock for <filename>" This is a side effect of the crash. When GnuCash opens a file, it locks it to prevent other users from opening at the same time. When the file is closed properly (eg by exiting GnuCash normally), this lock is removed again. However, if GnuCash crashes this lock remains. On the next startup, GnuCash detects this lock, but it can't possibly tell by itself whether it is there because the file is really still open, or if the program had crashed. So it has to ask the user.
Great! I figured the second error was from a read lock on the file, I just added that since I observed it. Thanks for the support
I am changing the title to reflect the exact problem. Also, this bug is related to bug#591177. Either this bug or bug #591177 will have to be fixed before 2.4. I'm tagging both for 2.3.x just to remember this.
*** Bug 610341 has been marked as a duplicate of this bug. ***
Created attachment 154315 [details] Backtrace on 2.3.10 linux crash with gtkhtml Turns out this is not a Windows-only bug, but apparently GtkHtml on linux is not used by the devs anymore. This backtrace was generated for GC 2.3.10 (svn tag 2.3.10), built with GtkHtml instead of WebKit on linux (Mandriva 2010.0) The segmentation fault is in the same function, but with the linux backtrace it's obvious the hist parameter is NULL, and this isn't tested for. Question is of course, why is it NULL ? I'll try to figure out which changeset caused this.
By the way, it's an ugly bug in that it's not fully consistent. Out of 10 attempts to make it crash, it happens about 7 times.
I went back as far as 2.3.6. The crash still happens there. Whatever is the cause must have been introduce before this. I can't go back further, because there are build errors with 2.3.5 on Mandriva 2010.0 with gtkhtml enabled.
I think I found the bugger. The gnc_html private object was not assigned to the gnc_html object in case of gtkhtml was used. Should be fixed as of r18702. We could test gtkhtml on windows again as a fix for the print problems in bug #591177 if we like (although at this moment the windows builds don't run due to a dll dependency issue, see bug #610348).
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=610051. Please update any external references or bookmarks.