Community
Participate
Working Groups
We have a number of warnings that are thrown into the console by SWT. This bug is to keep track of these warnings
I see lots of the following messages on the console: *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug
(In reply to Lars Vogel from comment #1) > I see lots of the following messages on the console: > > *** BUG *** > In pixman_region32_init_rect: Invalid rectangle passed > Set a breakpoint on '_pixman_log_error' to debug Do you know how to reproduce?
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=492709 for a repro for the "pixman_region32_init_rect" message.
We see this on resizing Eclipse window, with a new workspace and closed welcome page. Just make it smaller, bigger, smaller and one sees few of those errors. Interestingly this seem to report not always on resize, but only first time, as if there were some initialization issue or they have some internal counter. We get it on both Adwaita and Clearlooks-Phenix themes, so I assume this is theme independent. GTK is gtk3-3.14.13-16.el7.x86_64. SWT is 4.7.0 or also I20171018-2000.
So far on GTK 3.14 we mainly see the "invalid rectangle passed" error, on resize. On GTK 3.22, with Adwaita, we see a lot more: 1. On start-up. (Eclipse:30226): Gtk-WARNING **: Allocating size to GtkBox 0x7ffff06a6840 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (Eclipse:30226): Gtk-WARNING **: Allocating size to GtkBox 0x7ffff06a6840 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (Eclipse:30226): Gtk-WARNING **: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node trough, owner GtkProgressBar) (Eclipse:30226): Gtk-WARNING **: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node trough, owner GtkProgressBar) 2. After closing the Welcome window (if its a fresh workspace). (Eclipse:17065): Gtk-WARNING **: Allocating size to GtkBox 0x7ffff0ad3850 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? 3. Resizing Problems View (until the table contents / column headers nearly vanish) *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (Eclipse:15026): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width 13 and height -2 (Eclipse:15026): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar 4. When resizing a column in Problems View so that it has 0 width (Eclipse:30226): Gtk-WARNING **: Negative content width -2 (allocation 11, extents 6x7) while allocating gadget (node button, owner GtkButton) (Eclipse:30226): Gtk-WARNING **: Negative content width -6 (allocation 7, extents 6x7) while allocating gadget (node button, owner GtkButton) (Eclipse:30226): Gtk-WARNING **: Negative content width -11 (allocation 2, extents 6x7) while allocating gadget (node button, owner GtkButton) (Eclipse:30226): Gtk-WARNING **: Negative content width -12 (allocation 1, extents 6x7) while allocating gadget (node button, owner GtkButton) 5. Opening preferences (Window -> Preferences) (Eclipse:30226): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar (Eclipse:30226): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar (Eclipse:30226): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar (Eclipse:30226): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar 6. Expanding an item in the Preferences dialog, so that the item has elements below the bottom line of the tree (Eclipse:30226): Gtk-WARNING **: Allocating size to GtkScrolledWindow 0x7ffff07d0820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? 7. Make the preferences dialog smaller, selecting Run/Debug -> String substitution (Eclipse:17480): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkCheckButton
(In reply to Simeon Andreev from comment #5) > So far on GTK 3.14 we mainly see the "invalid rectangle passed" error, on > resize. > > On GTK 3.22, with Adwaita, we see a lot more: > > 1. On start-up. > > (Eclipse:30226): Gtk-WARNING **: Allocating size to GtkBox 0x7ffff06a6840 > without calling gtk_widget_get_preferred_width/height(). How does the code > know the size to allocate? > (Eclipse:30226): Gtk-WARNING **: Allocating size to GtkBox 0x7ffff06a6840 > without calling gtk_widget_get_preferred_width/height(). How does the code > know the size to allocate? > (Eclipse:30226): Gtk-WARNING **: Negative content width -1 (allocation 1, > extents 1x1) while allocating gadget (node trough, owner GtkProgressBar) > (Eclipse:30226): Gtk-WARNING **: Negative content width -1 (allocation 1, > extents 1x1) while allocating gadget (node trough, owner GtkProgressBar) > > 2. After closing the Welcome window (if its a fresh workspace). > > (Eclipse:17065): Gtk-WARNING **: Allocating size to GtkBox 0x7ffff0ad3850 > without calling gtk_widget_get_preferred_width/height(). How does the code > know the size to allocate? > > 3. Resizing Problems View (until the table contents / column headers nearly > vanish) > > *** BUG *** > In pixman_region32_init_rect: Invalid rectangle passed > Set a breakpoint on '_pixman_log_error' to debug > *** BUG *** > In pixman_region32_init_rect: Invalid rectangle passed > Set a breakpoint on '_pixman_log_error' to debug > (Eclipse:15026): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to > allocate widget with width 13 and height -2 > (Eclipse:15026): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion > 'size >= 0' failed in GtkScrollbar > > 4. When resizing a column in Problems View so that it has 0 width > > (Eclipse:30226): Gtk-WARNING **: Negative content width -2 (allocation 11, > extents 6x7) while allocating gadget (node button, owner GtkButton) > (Eclipse:30226): Gtk-WARNING **: Negative content width -6 (allocation 7, > extents 6x7) while allocating gadget (node button, owner GtkButton) > (Eclipse:30226): Gtk-WARNING **: Negative content width -11 (allocation 2, > extents 6x7) while allocating gadget (node button, owner GtkButton) > (Eclipse:30226): Gtk-WARNING **: Negative content width -12 (allocation 1, > extents 6x7) while allocating gadget (node button, owner GtkButton) > > 5. Opening preferences (Window -> Preferences) > > (Eclipse:30226): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion > 'size >= 0' failed in GtkScrollbar > (Eclipse:30226): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion > 'size >= 0' failed in GtkScrollbar > (Eclipse:30226): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion > 'size >= 0' failed in GtkScrollbar > (Eclipse:30226): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion > 'size >= 0' failed in GtkScrollbar > > 6. Expanding an item in the Preferences dialog, so that the item has > elements below the bottom line of the tree > > (Eclipse:30226): Gtk-WARNING **: Allocating size to GtkScrolledWindow > 0x7ffff07d0820 without calling gtk_widget_get_preferred_width/height(). How > does the code know the size to allocate? > > 7. Make the preferences dialog smaller, selecting Run/Debug -> String > substitution > > (Eclipse:17480): Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion > 'size >= 0' failed in GtkCheckButton This is on 4.8, correct?
(In reply to Eric Williams from comment #6) > This is on 4.8, correct? Yes, latest SWT state.
(In reply to Simeon Andreev from comment #7) > (In reply to Eric Williams from comment #6) > > This is on 4.8, correct? > > Yes, latest SWT state. Okay, thanks for confirming. I'm not sure how much work will go into warnings for 4.8, but I'm planning to revisit the warnings in 4.9. I believe the majority of the remaining warnings come from scrollbars.
Opened bug 533815 for 1. from comment 5 and bug 533799 for 3..
Continued reports for comment 5: Reported bug 534179 for 4. (negative content width warnings when a tree/table column to 0 width). Reported https://gitlab.gnome.org/GNOME/gtk/issues/210 for 5. (scrollbar critical errors on Window -> Preferences). My snippet for this is with a GtkTextView, but lets see what the GTK developers have to say. I'm guessing other widgets would have problems as well. Reported https://gitlab.gnome.org/GNOME/gtk/issues/197 (resp. bug 533876) for 6. (allocation size errors when expanding tree item).
(In reply to Simeon Andreev from comment #10) > Reported bug 534179 for 4. (negative content width warnings when a > tree/table column to 0 width). Do you have eclipse Bugzilla moderator rights? I could request them for you, to make it easier for you to add/remove dependencies and manage tickets.
Reported bug 534229 for 7. (assertion GtkCheckButton size >= 0) in comment 5, so far I have no SWT snippet for this (only reproduction steps in Eclipse). (In reply to Leo Ufimtsev from comment #11) > Do you have eclipse Bugzilla moderator rights? > I could request them for you, to make it easier for you to add/remove > dependencies and manage tickets. I believe I can only edit the related section of tickets that I opened myself. It would be nice if I can add related tickets myself, though. So if possible, please do!
(In reply to Simeon Andreev from comment #12) > I believe I can only edit the related section of tickets that I opened > myself. It would be nice if I can add related tickets myself, though. So if > possible, please do! Ok, we'll look into it next week after code freeze. This week we'll try to merge as many fixes as possible before code freeze.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
