Mailinglist Archive: opensuse-bugs (5243 mails)

< Previous Next >
[Bug 811214] New: Adwaita GTK2 engine leaking memory
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sat, 23 Mar 2013 20:32:46 +0000
  • Message-id: <bug-811214-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=811214

https://bugzilla.novell.com/show_bug.cgi?id=811214#c0


Summary: Adwaita GTK2 engine leaking memory
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
AssignedTo: bnc-team-gnome@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: gber@xxxxxxxxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---


Created an attachment (id=531337)
--> (http://bugzilla.novell.com/attachment.cgi?id=531337)
minimal test case

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101
Firefox/19.0

The new 3.6.x Adwaita GTK2 engine seam to leak memory in the cairo drawing code
used for drawing GtkProgressBars. The issue in particular manifests itself in
Xfce panel plugins such as xfce4-panel-plugin-diskperf,
xfce4-panel-plugin-cpugraph, and xfce4-panel-plugin-netload, see e.g.
https://bugzilla.novell.com/show_bug.cgi?id=777527 or
https://bugzilla.xfce.org/show_bug.cgi?id=9691.

I've created a minimal example for reproducing the issue and attached
corresponding valgrind logs, one with the GTK theme set to Adwaita and the
other with the theme set to Raleigh.

Compile with:

cc -g $(pkg-config --cflags --libs gtk+-2.0) -o gtk-leak gtk-leak.c

Use valgrind as follows:

export G_SLICE=always-malloc G_DEBUG=gc-friendly,resident-modules
timeout 300s valgrind --tool=memcheck --leak-check=full --leak-resolution=high
--num-callers=20 --log-file=gtk-leak.log ./gtk-leak


Reproducible: Always

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >