Bug 1969533
Summary: | Eclipse SWT Tree leaks native memory via gtk_tree_view_expand_row() | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Simeon Andreev <simeon.andreev> |
Component: | gtk3 | Assignee: | Matthias Clasen <mclasen> |
Status: | CLOSED MIGRATED | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.9 | CC: | akurtako, loskutov, mcoufal, otte, sbarcomb, vikpatil, vkadlcik |
Target Milestone: | rc | Keywords: | MigratedToJIRA |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-15 16:56: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: |
Description
Simeon Andreev
2021-06-08 14:40:19 UTC
We need either a GTK+ developer or a developer familiar with GTK3 API usage to look into this and let us know if: 1. This is a memory leak in GTK+. 1.1. In this case we need a fix in GTK+, which we require to resolve this support case. 2. SWT is supposed to use different API to remove tree rows, to avoid leaking memory. 2.1. We need to know what API we are supposed to use, to remove tree rows without causing a memory leak. 2.2. We need to know what to expect of the new code performance-wise. E.g. should we expect massive performance degradation? RHEL support case: https://access.redhat.com/support/cases/#/case/02959748 Simeon, please change title. It is not Eclipse nor SWT that leaks memory here, but GTK library via gtk_tree_view_expand_row(). Also the "component" is wrong, it must be GTK. (In reply to Andrey Loskutov from comment #3) > Simeon, please change title. It is not Eclipse nor SWT that leaks memory > here, but GTK library via gtk_tree_view_expand_row(). Also the "component" > is wrong, it must be GTK. We don't know whether SWT is misusing GTK+ APIs to cause the memory leak, see comment 2. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |