Fogger does not close opened processes

Bug #1053506 reported by Jacob Winski on 2012-09-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Newest Fogger from PPA:
$ /usr/bin/python /opt/ --version

After closing the Fogger window Fogger processes are not closed. Every process Fogger opened stays opened. If Fogger is opened multiple times, every single process stays after closing. This means hundreds of open processes after using Fogger for a few days.

What is weird is that sometimes this happens, sometimes it closes. Sometime it does a "clean" close, other times it coredumps but still closes the process. When it does not close the process, it always has a glibc error. When it does close the process, there is never a glibc error.

Note: Anything in <....> has been replaced by me (username, id's, etc.).

~~~~ Example of Fogger when it does not close process ~~~~
$ /usr/bin/python /opt/ <id withheld>
$ ps -ef | grep fogger
<username> 29902 28098 15 17:45 pts/2 00:00:04 /usr/bin/python /opt/ <id withheld>
[close fogger window]
$ ps -ef | grep fogger
<username> 29902 28098 9 17:45 pts/2 00:00:06 /usr/bin/python /opt/ <id withheld>
$ /usr/bin/python /opt/ <id withheld>
[close fogger window]
~$ ps -ef | grep fogger
<username> 29902 28098 4 17:45 pts/2 00:00:06 /usr/bin/python /opt/ <id withheld>
<username> 29982 1 12 17:47 ? 00:00:03 /usr/bin/python /opt/ <id withheld>
$ /usr/bin/python /opt/ <id withheld>
[close fogger window]
$ ps -ef | grep fogger
<username 29902 28098 1 17:45 pts/2 00:00:06 /usr/bin/python /opt/ <id withheld>
<username> 29982 1 2 17:47 ? 00:00:06 /usr/bin/python /opt/ <id withheld>
<username> 30268 30055 18 17:51 pts/4 00:00:03 /usr/bin/python /opt/ <id withheld>

So on and so forth. Part of the output from these processes:
*** glibc detected *** /usr/bin/python: corrupted double-linked list: 0x0000000002f0a810 ***

Another process had this glibc error instead:
*** glibc detected *** /usr/bin/python: malloc(): memory corruption: 0x00000000038a7220 ***

~~~~ Example of correctly functioning Fogger ~~~~
$ /usr/bin/python /opt/ <id withheld>
$ ps -ef | grep fogger
<username> 29595 28098 99 17:38 pts/2 00:00:44 /usr/bin/python /opt/ <id withheld>
[close fogger window]
$ ps -ef | grep fogger
[nothing shown]

No glibc error.

After trying different fogapps (two GMail, two Google Apps Gmail, one Google+), the only thing I noticed in the output was that when fogger would not close the process there was always a glibc error. That is the only output that the bad fogger process had in common. For these tests I have tried opening different fogapps about 50 times.

Jacob Winski (winski) wrote :

More system information:

$ python --version
Python 2.7.3

$ cat /etc/lsb-release

Am I the only one with this *** glibc detected *** error? Fogger is so awesome, but with this glibc problem totally unusable.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers