Bluefish crashes when saving a lot of open files

Bug #1164472 reported by André Barmasse
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluefish (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When I open a lot of files (around 20 and more) and search/replace text in them and then try to save all open documents, Bluefish sometimes does not save all the files. Instead, the program opens a window telling me that some files are about to be saved, but nothing happens then. I have to kill Bluefish from the bash. Relaunching Bluefish, the unstored files appear again, but without syntax highlighting, and saving them is not possible.

In connection with that bug might be, that Bluefish has sometimes major problems searching/replacing major blocks of code. Sometimes it does not replace it everywhere, sometimes it scrambles existing code and scatters the code, that should be inserted, in small pieces randomly into the existing code. Very ugly! Trying to store such files mostly crashes Bluefish.

I have attached a part of the command line output, created just before such a crash. I hope it can help.

Good luck! André

------------------------------

(bluefish:2380): Gtk-CRITICAL **: gtk_tree_path_get_depth: assertion `path != NULL' failed

(bluefish:2380): Gtk-CRITICAL **: gtk_tree_path_get_depth: assertion `path != NULL' failed
Possible error in language file, id - / pattern } has ends_context=2, but has only 2 parent contexts
Error in language file, blockstartelement e.css.lbrace does not exist
Error in language file, context id c.css.pseudo already exists
Possible error in language file, id - / pattern } has ends_context=2, but has only 1 parent contexts
Language statistics for CSS from /usr/share/bluefish/bflang//css.bflang2
reference size 0.00 Kbytes
largest table 1032 ( 258.00 Kbytes)
total tables 8119 ( 2029.75 Kbytes)
contexts 86 ( 4.03 Kbytes)
matches 1338 ( 62.72 Kbytes)
blocks 1 ( 0.03 Kbytes)
scancache integrity check done in 0.246000 ms.
Possible error in language file, id - / pattern } has ends_context=2, but has only 2 parent contexts
Possible error in language file, id end-style-tag / pattern </style> has ends_context=3, but has only 3 parent contexts
Language statistics for PHP from /usr/share/bluefish/bflang//php.bflang2
reference size 0.00 Kbytes
largest table 32005 ( 8001.25 Kbytes)
total tables 51355 ( 12838.75 Kbytes)
contexts 192 ( 9.00 Kbytes)
matches 8129 ( 381.05 Kbytes)
blocks 14 ( 0.44 Kbytes)
Possible error in language file, no textstyle found for highlight css-draft-property

(bluefish:2380): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(bluefish:2380): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(bluefish:2380): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(bluefish:2380): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(bluefish:2380): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(bluefish:2380): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(bluefish:2380): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(bluefish:2380): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(bluefish:2380): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
scancache integrity check done in 2.393001 ms.
scancache integrity check done in 2.344998 ms.
scancache integrity check done in 0.675000 ms.
scancache integrity check done in 0.293000 ms.
scancache integrity check done in 0.254000 ms.
scancache integrity check done in 0.275000 ms.
scancache integrity check done in 0.275999 ms.
scancache integrity check done in 0.256000 ms.
scancache integrity check done in 0.809000 ms.
scancache integrity check done in 0.736000 ms.
scancache integrity check done in 0.708000 ms.
scancache integrity check done in 0.807000 ms.
scancache integrity check done in 0.647000 ms.
scancache integrity check done in 0.273000 ms.
scancache integrity check done in 0.301000 ms.
scancache integrity check done in 0.262001 ms.
scancache integrity check done in 0.277000 ms.
scancache integrity check done in 0.253000 ms.
scancache integrity check done in 0.275000 ms.

(bluefish:2380): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

(bluefish:2380): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
scancache integrity check done in 0.329000 ms.
scancache integrity check done in 0.299000 ms.
scancache integrity check done in 0.113000 ms.
scancache integrity check done in 0.550000 ms.

(bluefish:2380): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
scancache integrity check done in 0.663001 ms.
scancache integrity check done in 2.428999 ms.
scancache integrity check done in 2.295000 ms.
scancache integrity check done in 2.268001 ms.

description: updated
Revision history for this message
OlivierS (olivier-olivier) wrote :

which version of bluefish are you using?

Revision history for this message
Paul White (paulw2u) wrote :

André,

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Your problem may have been fixed with some of the updates.

It would help us a lot if you could test on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once in a terminal:

apport-collect 1164472

and then change the status back to "New".

Please also add any additional information that you think might be relevant. Alternatively, please confirm that this is no longer a problem and that we can the report. If we do not hear from you this bug report will expire in approximately 60 days time.

Thank you again for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in bluefish (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for bluefish (Ubuntu) because there has been no activity for 60 days.]

Changed in bluefish (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.