Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2032438

Summary: [GTK3] gtk_tree_view_set_cursor() leaks memory for trees with multiple renderers
Product: Red Hat Enterprise Linux 8 Reporter: Tomas Popela <tpopela>
Component: gtk3Assignee: David King <dking>
Status: CLOSED ERRATA QA Contact: Radek Duda <rduda>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.6CC: desktop-qa-list, dking, mclasen, otte, sbarcomb, simeon.andreev, tpelka, tpopela
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gtk3-3.22.30-10.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1965195 Environment:
Last Closed: 2022-05-10 14:26:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1965195    
Bug Blocks:    

Comment 1 David King 2022-01-17 17:44:00 UTC 
Backport builds fine locally.
Comment 2 Radek Duda 2022-01-31 14:17:30 UTC 
Similarly as https://bugzilla.redhat.com/show_bug.cgi?id=1965195 this is not corrected. I am attaching valgrind logs of #c0 table script for comparison of new gtk3-3.22.30-9 and old gtk3-3.22.30-8 version. The memory leak is bigger now.

gcc -g table.c  `pkg-config --cflags --libs gtk+-3.0`  -o table
valgrind --leak-check=full ./table
Comment 7 Radek Duda 2022-02-15 13:01:14 UTC 
I tested with new build gtk3-3.22.30-10.el8 and see still some leak.
The leak is now smaller then in the case of gtk3-3.22.30-9 or gtk3-3.22.30-8 and it does not seem to leak directly from the script of this bug report (https://bugzilla.redhat.com/show_bug.cgi?id=2032438#c0).
I am not sure whether this leak is acceptable.
Is this leak expected Matthias? (see attached valgrind report)
Comment 9 Matthias Clasen 2022-02-15 15:43:06 UTC 
If you use valgrind on gtk applications, please use the suppressions file that is shipped with gtk, https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/gtk.supp
Comment 10 Matthias Clasen 2022-02-15 15:44:19 UTC 
The leaks in that log are indeed expected, and should be suppressed by that suppressions file. There are no a11y related leaks left, afaics.
Comment 11 Radek Duda 2022-02-16 12:21:04 UTC 
ok got it: 
valgrind --leak-check=full --show-leak-kinds=all  --suppressions=/home/test/gtk.supp ./table

==21311== LEAK SUMMARY:
==21311==    definitely lost: 0 bytes in 0 blocks
==21311==    indirectly lost: 15,925 bytes in 680 blocks
==21311==      possibly lost: 3,764 bytes in 36 blocks
==21311==    still reachable: 2,019,034 bytes in 24,561 blocks
==21311==                       of which reachable via heuristic:
==21311==                         length64           : 7,568 bytes in 119 blocks
==21311==                         newarray           : 2,272 bytes in 62 blocks
==21311==         suppressed: 3,600 bytes in 24 blocks
==21311==
==21311== For lists of detected and suppressed errors, rerun with: -s
==21311== ERROR SUMMARY: 34 errors from 34 contexts (suppressed: 8 from 8)
Comment 17 errata-xmlrpc 2022-05-10 14:26:04 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (gtk3 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1946