GNOME Bugzilla – Bug 328459
Bluefish crashes seemingly randomly after some use
Last modified: 2006-08-24 03:38:01 UTC
Steps to reproduce: I can't reproduce the bug. It occurs seemingly randomly after some use. Here is what has caused the crash so far: 1) I indented about 20 lines of text several times in quick succession. CPU was under severe load when it happened. I could not reproduce the event. 2) Tried changing background colour for a highlighting parameter. Applied changes and hit F5 to update. On hitting F5, bluefish crashed. Again, cannot reproduce. 3) Selected and deleted about 5 chars of text. I wonder if undo buffer is maxing out. Stack trace: So far I've not had any luck getting a back-trace. As soon as I get one, I'll post it. Other information:
I cannot reproduce the bug either, but I've noticed with an html file made of 60 lines, only with p, il, li tags and a href ones, the cpu raises to 35% when applying changes in hightlighting colors in preferences pane, and to 15% when refreshing the hightlights in document with F5. Crashes occur frequently by me when opening two files (say po files in bluefish are good candidates). Working on both files; closing one of them, then attempting to close the second one -> crash fully reproducable. It might be that this has to do with the hightlight refreshing (fixed to 5 lines here).
Created attachment 58224 [details] last 100 lines of bluefish backtrace before it crashed Here's that backtrace
Created attachment 58251 [details] Backtrace crashing when closing document bluefish-unstable gzipped file
David, I may have fixed the GLib-CRITICAL warnings in comment #2. I couldn't reproduce them, but I found an issue in bf_textview_insert_text_cb(). It looks like that may have been where they were coming from. Michele, comment #3, do you have any debugging output in addition to the bt? Uncomment the #define DEBUG at the the top of menu.c and recompile.
Created attachment 58374 [details] gzipped acktrace from gdb After doing some replace in two files and clicking rapidly on save and close on both files.
I've not had any problems since Jim fixed the GLib-CRITICAL warnings, so I think it's fixed. Should we close this now?
Going to close this as fixed. David, reopen it if the problem reappears.