GNOME Bugzilla – Bug 167905
Memory Leak
Last modified: 2005-02-19 22:59:22 UTC
Distribution: Slackware Slackware 10.1.0 Package: gnome-panel Severity: critical Version: GNOME2.6.2 2.6.x Gnome-Distributor: GNOME.Org Synopsis: Memory Leak Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: Memory Leak Steps to reproduce the crash: 1. When I changed a gnome-panel Main Menu bar, and disabled the expand option, then placed it in the top-right hand corner. All of a sudden it starts shaking left and right. Not functional; however I can right-click on the button next to the "quick-command console" but nothing happens, the context menu pops up, but it is also unfunctional. 2. The main reason I'm submitting this is because I've deleted all sorts of .configdirs for metacity, gnome* this gnome* that. I wish I could delete the settings for the GNOME desktop without having to destroy my whole home directory. I've been searching newsgroups and I can't find anything either. 3. thanks for any feedback. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (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) (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) [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 3259)] (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) 0x40ba0488 in waitpid () from /lib/libpthread.so.0
+ Trace 55888
Thread 1 (Thread 16384 (LWP 3259))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-19 15:46 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-panel". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was bradynorman@gmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
It looks like you've reported three separate bugs, because nowhere in your description did you state that your changes appeared to cause a crash, nor did it mention any kind of memory leak as you did in the summary. That means that if there really are three separate bugs, then you should file separate bug reports. Anyway, the stack trace matches the one in bug 146075 so I'll mark it as a duplicate. *** This bug has been marked as a duplicate of 146075 ***