GNOME Bugzilla – Bug 115666
edit po and playing with alt+2 give a crash
Last modified: 2009-08-15 18:40:50 UTC
Package: gtranslator Severity: blocker Version: 1.0 Synopsis: edit po and playing with alt+2 give a crash Bugzilla-Product: gtranslator Bugzilla-Component: Parse engine Description: Description of Problem: another crash, to me seems something related to fuzzy unfuzzy change using alt+2 Steps to reproduce the problem: 1. open a file translate some string 2. set unset for some string the fuzzy property 3. do it several time seem that doing it quickly crash the engine Actual Results: crash Expected Results: no crash How often does this happen? quite often Additional Information: the property unfuzzy after translation is disabled Debugging Information: Backtrace was generated from '/usr/bin/gtranslator' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 3319)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...0x407ce452 in mallopt () from /lib/libc.so.6
+ Trace 38036
Thread 1 (Thread 16384 (LWP 3319))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-21 10:50 ------- Unknown version unspecified in product gtranslator. Setting version to "0.38". Reassigning to the default owner of the component, ross@golder.org.
*** Bug 115669 has been marked as a duplicate of this bug. ***
The stack trace looks similar to the ones in bug 98308, bug 98308, and bug 112548 (which had some potentially interesting comments at the end). Each of these bug reports was on a Debian testing/unstable system.
A better stacktrace, for the record... 0x407d23d9 in mallopt () from /lib/libc.so.6 (gdb) bt
+ Trace 38928
-- Ross
When you press Alt+2, it takes a short while (less than half a second) for the GUI to be updated. If the key is pressed before the GUI is updated, a segfault is generated. Using CVS HEAD, I now get the following stacktrace if I repeatedly press Alt+2: (gdb) bt
+ Trace 39472
I'm lowering the priority and severity, as most people would not repeatedly switch this value in normal use.
This can also be reproduced by pressing Alt+2 four times on a particular message, although different things happen each time. Sometimes it enters some kind of endless loop. Other times, it segfaults (in one of a number of places). This is looking more like a bug in the one of the libraries (likely gtk+).
I'd say nobody shall press 4x Alt-2 in a half minute and this does now also sound löike a more engineering problem on Gtk+ then of us in the app code of gtranslator. So it's no bug of us, so it's NOTABUG ;-)