After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 510278 - gtk.statusicon leaking under windows
gtk.statusicon leaking under windows
Status: RESOLVED INCOMPLETE
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.12.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-01-17 21:41 UTC by Yann Leboulanger
Modified: 2009-03-29 03:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test python script (429 bytes, text/x-python)
2008-01-17 22:09 UTC, Yann Leboulanger 		Details

Description Yann Leboulanger 2008-01-17 21:41:47 UTC 
Steps to reproduce:
1. take 2 images 16x16 (online.png and away.png) from http://trac.gajim.org/browser/trunk/data/iconsets/sun/16x16
2. Put the attached script in the same folder
3. Run it.

in process manager I see used mem growing and growing.

same script under linux doesn't seem to leak


Stack trace:


Other information:
Comment 1 Yann Leboulanger 2008-01-17 22:09:47 UTC 
Created attachment 103094 [details]
test python script
Comment 2 Paul Pogonyshev 2008-01-18 22:13:03 UTC 
Lowering severity, this is not critical.
Comment 3 Yann Leboulanger 2008-01-20 10:52:28 UTC 
it makes my application crash after several days under windows...
Comment 4 Paul Pogonyshev 2008-01-20 15:45:15 UTC 
I'm not sure it is PyGTK-specific, no apparent errors in PyGTK code.  Can you test with GTK+ itself?
Comment 5 Paul Pogonyshev 2008-01-20 15:48:41 UTC 
See bug 364868.  I guess updating GTK+ would help.
Comment 6 Yann Leboulanger 2008-01-20 16:39:33 UTC 
it seems this patch was applied in 2.10. I tried with 2.12 and bug is still here.

But maybe you're right that it's not PyGTK specific. Unfortunatly I never use Windows, so I don't have a C environment to test, and I don't have much time :/
Comment 7 Gian Mario Tagliaretti 2008-09-01 21:32:50 UTC 
I can be wrong but this looks like a problem of GTK+ on win32 (sorry I cannot test it though).

If it's not GTK+/win32 please move it back and hopefully someone will test it with the latest gtk/pygtk 2.13.x on windows.
Comment 8 Tor Lillqvist 2008-09-02 07:23:36 UTC 
When running this against GTK+ 2.12.11 I see absolutely no increase in memory usage or handle count. I even lowered the delay to 

Are you sure you tried against GTK+ 2.12, and were not mislead by some older GTK+ copy you didn't remember being present in PATH (or, brrr, system32)? Please use Process Explorer from sysinternals to verify that the GTK+ DLLs loaded into the python process when running the code are those that you expect.
Comment 9 Tobias Mueller 2009-03-29 03:15:27 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!