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 665659 - GtkScrolledWindow: unset the child's adjustments after removing it.
GtkScrolledWindow: unset the child's adjustments after removing it.
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkScrolledWindow
3.22.x
Other All
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks: 660347
 
 
Reported: 2011-12-06 09:29 UTC by Krzesimir Nowak
Modified: 2018-05-02 15:16 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Scrolledwindow: unset adjustments after removal, not before. (1.11 KB, patch)
2011-12-06 09:29 UTC, Krzesimir Nowak 		none Details | Review

Description Krzesimir Nowak 2011-12-06 09:29:40 UTC 
Created attachment 202902 [details] [review]
Scrolledwindow: unset adjustments after removal, not before.

It would be good to have adjustments unsetting be done after removing child, not before, because that causes useless redraws of a child. Also, that sometimes cause crashes in gtkmm during disposal, because unsetting adjustments causes size recomputation of a child and that calls some virtual functions of an already destroyed C++ wrapper at that time. See bug 660347.
Comment 1 Murray Cumming 2012-02-10 16:44:24 UTC 
May we please push this. It fixes a crash in at least one gtkmm-using application.
Comment 2 Murray Cumming 2013-10-27 19:37:53 UTC 
This still seems like a good idea.
Comment 3 Daniel Boles 2017-09-04 22:12:03 UTC 
The current code still does what it did when this was opened. Is this still known to cause problems?
Comment 4 GNOME Infrastructure Team 2018-05-02 15:16:25 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/376.