Mailinglist Archive: opensuse-bugs (6406 mails)
| < Previous | Next > |
[Bug 256363] Kbabel has a huge memory hole (2 GiB)
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Sun, 1 Apr 2007 08:57:47 -0600 (MDT)
- Message-id: <20070401145747.30A4325C887@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=256363
robin.listas@xxxxxxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|robin.listas@xxxxxxxxxxxxxx |
------- Comment #11 from robin.listas@xxxxxxxxxxxxxx 2007-04-01 08:57 MST -------
Ok.
I found that the crash depends on the database: I had deleted and recreated it
and couldn't make kbabel eat memory.
The good news is that I had kept a backup copy, just in case, restored it, and
can make kbabel crash it any time I want (select project, select po file,
select package, go to next untranslated message, select button to search in
dictionay of translation database (eqv to ^2).
The bad news is that I don't get a backtrace:
cer@nimrodel:~> ulimit -v 300000
cer@nimrodel:~> kbabel
cer@nimrodel:~> terminate called after throwing an instance of 'St9bad_alloc'
what(): St9bad_alloc
KCrash: Application 'kbabel' crashing...
Error: Could not determine display.
KCrash cannot reach kdeinit, launching directly.
cer@nimrodel:~>
I don't have a "KCrash" app that I can find, nor via yast install. If it wants
kdeinit, it is indeed running:
24488 ? S 0:00 start_kdeinit --new-startup +kcminit_startup
24489 ? Ss 0:00 kdeinit Running...
24494 ? S 0:00 \_ klauncher [kdeinit] --new-startup
24504 ? S 0:01 \_ kwin [kdeinit] -session
10ddcdd2de000117278085700000308410000_1175437963_469787
24509 ? S 0:00 \_ kio_file [kdeinit] file
/tmp/ksocket-cer/klauncherTeRNKb.slave-socket /tmp/ksocket-c
er/kdesktopMq64nc.slave-socket
24526 ? S 0:00 \_ konqueror [kdeinit] --preload
24653 ? S 0:01 \_ konsole [kdeinit]
24654 pts/1 Ss+ 0:00 | \_ /bin/bash
24711 pts/2 Ss 0:00 | \_ /bin/bash
24817 pts/2 R+ 0:00 | \_ ps afx
24818 pts/2 S+ 0:00 | \_ less
24770 ? S 0:00 \_ /bin/sh /usr/bin/firefox
24775 ? Sl 0:19 \_ /usr/lib/firefox/firefox-bin
24784 ? Z 0:00 \_ [netstat] <defunct>
If it is trying to start something directly, wouldn't it be affected by ulimit
too? Can I start some program before hand to handle the backtrace? Or can I
make ulimit affect only kbabel and nothing else? Do you want me to run strace
or ltrace and repeat the crash?
I'm willing to help trace the bug, but my knowledge is limited.
I may attach the backup of the database that produces the memory hole, if you
want it; but even if the database is corrupt, memory holes should not happen,
and databases should have a method to clean themselves, IMO.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
robin.listas@xxxxxxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|robin.listas@xxxxxxxxxxxxxx |
------- Comment #11 from robin.listas@xxxxxxxxxxxxxx 2007-04-01 08:57 MST -------
Ok.
I found that the crash depends on the database: I had deleted and recreated it
and couldn't make kbabel eat memory.
The good news is that I had kept a backup copy, just in case, restored it, and
can make kbabel crash it any time I want (select project, select po file,
select package, go to next untranslated message, select button to search in
dictionay of translation database (eqv to ^2).
The bad news is that I don't get a backtrace:
cer@nimrodel:~> ulimit -v 300000
cer@nimrodel:~> kbabel
cer@nimrodel:~> terminate called after throwing an instance of 'St9bad_alloc'
what(): St9bad_alloc
KCrash: Application 'kbabel' crashing...
Error: Could not determine display.
KCrash cannot reach kdeinit, launching directly.
cer@nimrodel:~>
I don't have a "KCrash" app that I can find, nor via yast install. If it wants
kdeinit, it is indeed running:
24488 ? S 0:00 start_kdeinit --new-startup +kcminit_startup
24489 ? Ss 0:00 kdeinit Running...
24494 ? S 0:00 \_ klauncher [kdeinit] --new-startup
24504 ? S 0:01 \_ kwin [kdeinit] -session
10ddcdd2de000117278085700000308410000_1175437963_469787
24509 ? S 0:00 \_ kio_file [kdeinit] file
/tmp/ksocket-cer/klauncherTeRNKb.slave-socket /tmp/ksocket-c
er/kdesktopMq64nc.slave-socket
24526 ? S 0:00 \_ konqueror [kdeinit] --preload
24653 ? S 0:01 \_ konsole [kdeinit]
24654 pts/1 Ss+ 0:00 | \_ /bin/bash
24711 pts/2 Ss 0:00 | \_ /bin/bash
24817 pts/2 R+ 0:00 | \_ ps afx
24818 pts/2 S+ 0:00 | \_ less
24770 ? S 0:00 \_ /bin/sh /usr/bin/firefox
24775 ? Sl 0:19 \_ /usr/lib/firefox/firefox-bin
24784 ? Z 0:00 \_ [netstat] <defunct>
If it is trying to start something directly, wouldn't it be affected by ulimit
too? Can I start some program before hand to handle the backtrace? Or can I
make ulimit affect only kbabel and nothing else? Do you want me to run strace
or ltrace and repeat the crash?
I'm willing to help trace the bug, but my knowledge is limited.
I may attach the backup of the database that produces the memory hole, if you
want it; but even if the database is corrupt, memory holes should not happen,
and databases should have a method to clean themselves, IMO.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
| < Previous | Next > |