Bug 187764 - Lokalize crashes when moving on to the next entry
Summary: Lokalize crashes when moving on to the next entry
Status: RESOLVED BACKTRACE
Alias: None
Product: lokalize
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Nick Shaforostoff
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-21 06:24 UTC by Franklin Weng
Modified: 2009-05-20 02:28 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Franklin Weng 2009-03-21 06:24:28 UTC
Version:            (using KDE 4.2.1)
OS:                Linux
Installed from:    Mandriva RPMs

I'm using KDE 4.2.1 from Mandriva packages.  But this problem happened from 4.1 I think.

When I translated with lokalize, sometimes I used PageDown to move to the next entry, and lokalize crashed quietly.  No error report dialog.  So I tried to launch lokalize from command line, and turn on the core dump size.  However, when it crashed, no core dumped.  It returned "Alarm" then.

Here are the last messages while crashing:

lokalize(10500) KAiderView::approvedEntryDisplayed: approvedEntryDisplayed. entry: 162 approved: true                                                           
lokalize(10500) Catalog::flushUpdateDBBuffer: updating!!                        
KCrash: Application 'lokalize' crashing...                                      
Alarm

All my unsaved work were gone.  Even those translated entries were not recorded in the translation memory.  I wondered if this problem was related to the translation database.  I installed qt4-database-plugin-sqlite-4.5.0-1mdv2009.0.
Comment 1 Nick Shaforostoff 2009-03-21 21:01:38 UTC
which platform do you use? (64-bit or 32-bit).

there was similar report #185144 , with Qt 4.5 on amd 64. never could reproduce it though.
Comment 2 Franklin Weng 2009-03-22 02:12:15 UTC
Yes, similar, but a bit different.  I got SIGALRM instead of SIGABRT, and no backtrace.

I'm using 32-bit system.

Well, maybe not SIGALRM?  I don't really mean what "Alarm" meant.
Comment 3 Nick Shaforostoff 2009-03-22 09:24:00 UTC
i'm sure this is Qt 4.5 related bug. if you compile Qt 4.4 yourself and install it locally (+ madify LD_LIBRARY_PATH to make your system search in local dir first), Lokalize will stop crashing.

I know at least one Qt 4.5 related problem that was fixed in branch svn (i.e. KDE 4.2.2) (bug 187219), so compiling lokalize from svn might help.

Also, as you're already using Qt 4.5, you might want to compile kdelibs+lokalize from trunk to get autosave feature (at least you won't loose a lot of data anymore).
Comment 4 Nick Shaforostoff 2009-03-22 09:25:20 UTC
of course, if you see the crashes are reproducible on certain entries of certain files, do send me them.
Comment 5 Franklin Weng 2009-05-12 03:08:05 UTC
I found a way that may reproduce this problem easier.

For a file that contains many fuzzy or untranslated entries, if I push and hold alt-pgdown (or alt-pgup) to go through the untranslated messages, it would crash sometimes.  Pushing and holding ctrl-pgdown or ctrl-pgup was similar.
Comment 6 Nick Shaforostoff 2009-05-12 03:32:05 UTC
which lokalize version do you you use?

you can try running lokalize under gdb:

'gdb lokalize' <enter>
r <enter>
(got a crash)
bt <enter>

also try compiling lokalize yourself, this will add debug info to the executable
http://userbase.kde.org/Lokalize#Compiling_Lokalize_from_trunk_under_KDE_4.2
(but checkout form 4.2 branch, not trunk)
Comment 7 Nick Shaforostoff 2009-05-19 17:04:43 UTC
this is most likely a dup of #191122 .
Comment 8 Franklin Weng 2009-05-20 01:43:04 UTC
Not sure.  The symptom was not quite matched, but we can see if it could be fixed in KDE 4.3.
Comment 9 Nick Shaforostoff 2009-05-20 02:22:33 UTC
how often do experience such crashes?
Comment 10 Franklin Weng 2009-05-20 02:28:24 UTC
Quite often... maybe one fourth or one fifth.

Just experienced another crash 15 minutes ago... *sigh*