Kicker needs more RAM? St9bad_alloc

sloik2000 · 04-14-2005, 05:30 AM

Hey guys.
I just upgraded to KDE, and a few days ago, just out of the blue, the KDE kicker stopped working with this in the terminal:

Code:

[hayden@mcafee ~]$ terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc
kicker: crashHandler called
KCrash: Application 'kicker' crashing...
terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc

I found this URL, and I think it may explain the situation. URL
I just want to make sure it is a RAM problem before getting more RAM. I currently have 386 mb I believe, of RAM. And if it is a RAM problem, why wasn't it happening before?

Thanks,
-Sloik

trickykid · 04-14-2005, 06:11 AM

Memory leaks.. or did you start running more services or applications.. ? "My car stopped working today, but it worked yesterday?" Could be anything really..

sloik2000 · 04-14-2005, 02:31 PM

No, not that I know of

Well, If it is memory leaks, how could I fix them? Do I need new RAM?

Thanks for the reply,
-Sloik

{EDIT} I just logged in to my sister's account, and her kicker works! So it's only me I guess. Well, here's the backtrace to the crash thing that comes up after it crashes.

Code:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1231096128 (LWP 6513)]
[KCrash handler]
#4  0xb7fe87a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#5  0xb6b617d5 in raise () from /lib/tls/libc.so.6
#6  0xb6b63149 in abort () from /lib/tls/libc.so.6
#7  0xb6d2eb0b in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#8  0xb6d2c821 in __cxa_call_unexpected () from /usr/lib/libstdc++.so.6
#9  0xb6d2c856 in std::terminate () from /usr/lib/libstdc++.so.6
#10 0xb6d2c99f in __cxa_throw () from /usr/lib/libstdc++.so.6
#11 0xb6d2cdec in operator new () from /usr/lib/libstdc++.so.6
#12 0xb6d2ce89 in operator new[] () from /usr/lib/libstdc++.so.6
#13 0xb73db07e in QString::setLength () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#14 0xb73e3519 in operator>> () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#15 0xb6560842 in kdemain () from /usr/lib/kde3/klipper_panelapplet.so
#16 0xb656155b in kdemain () from /usr/lib/kde3/klipper_panelapplet.so
#17 0xb6562e29 in kdemain () from /usr/lib/kde3/klipper_panelapplet.so
#18 0xb655cd2e in ?? () from /usr/lib/kde3/klipper_panelapplet.so
#19 0x08220a78 in ?? ()
#20 0x08215938 in ?? ()
#21 0x08220bc8 in ?? ()
#22 0x00000001 in ?? ()
#23 0xb6573776 in typeinfo name for KAboutApplication ()
   from /usr/lib/kde3/klipper_panelapplet.so
#24 0xb6c61800 in __malloc_initialize_hook () from /lib/tls/libc.so.6
#25 0x0000014c in ?? ()
#26 0xb6d4de6c in ?? () from /usr/lib/libstdc++.so.6
#27 0x0000014c in ?? ()
#28 0x08215938 in ?? ()
#29 0xbfffe368 in ?? ()
#30 0x08220a78 in ?? ()
#31 0x082158d0 in ?? ()
#32 0x08215938 in ?? ()
#33 0xbfffe368 in ?? ()
#34 0xb7142eed in QWidget::setBackgroundMode ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#35 0xb655ce2a in ?? () from /usr/lib/kde3/klipper_panelapplet.so
#36 0x08220a78 in ?? ()
#37 0x08215938 in ?? ()
#38 0x00000000 in ?? ()

Also, on the Crash popup, it states that "The application KDE Panel (kicker) crashed and caused the signal 6 (SIGABRT)."
Help!

sloik2000 · 04-15-2005, 08:13 PM

How can I just reinstall kicker? This is getting extremely annoying!

Please Help!
-Sloik

GrzegorzD · 05-09-2005, 12:33 PM

Just delete file history.lst located in ~/.kde/share/apps/kicker and kicker will work - for some weeks.
I don't think it has somthing to do with memory leaks - in my machine kicker "plays dead" even just after reset - it must be very fast memory leak

mhearn · 05-10-2005, 11:49 AM

It looks like a bug in KDE: probably not checking the length of a string or list before trying to load it.