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 707412 - Notebook tabs set to a position other than GTK_POS_TOP leak GDI objects
Notebook tabs set to a position other than GTK_POS_TOP leak GDI objects
Status: RESOLVED DUPLICATE of bug 547656
Product: gtk+
Classification: Platform
Component: Widget: GtkNotebook
2.24.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-09-03 18:07 UTC by Grant Garcia
Modified: 2014-02-21 21:16 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Simple program demonstrating the leak. (587 bytes, application/octet-stream)
2013-09-03 18:07 UTC, Grant Garcia 		Details

Description Grant Garcia 2013-09-03 18:07:13 UTC 
Created attachment 254007 [details]
Simple program demonstrating the leak.

When notebook tabs are assigned a position of GTK_POS_(LEFT|RIGHT|BOTTOM), switching tabs, resizing the window, focusing/unfocusing the window, etc. all cause GDI objects to leak. Resizing the window in particular can leak hundreds or even thousands of GDI objects per second, causing the object count to approach Windows' hard limit of 10,000 per process rather quickly.

I'm running Windows 7 and building with the GTK 2.24.10 bundle.
Comment 1 Bob the Hamster 2013-10-29 16:46:24 UTC 
I have a program I am working on which uses a lot of NoteBook tabs, all of which are positioned BOTTOM.

I can reproduce this bug consistently on both Windows XP and Windows 7. I am using the latest stable gtk all-in-one installer 2.24.2

Grant: Thanks for narrowing this down to non-TOP notebooks. I really hope someone can fix this for the next stable release!
Comment 2 William Jon McCann 2014-02-21 21:16:29 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 547656 ***