Александър Куртаков

No reply taking it as no longer of interest.

@vogella Please note that SWT has been compiled with gtk 4 support but launcher isn't and this is most likely what fails for you. Use the launcher.jar and not executable...

I consider this one done via https://github.com/eclipse-equinox/equinox/pull/1118 . Any problem one may still have - please open a dedicated issue so it can be investigated further.

Issue is fixed in alternative way https://github.com/eclipse-platform/eclipse.platform.swt/pull/2472

Neither test execution order nor bundle build time are fixed, this makes it almost impossible why the OOM happens on Jenkins IMO. My way to work towards this is to...

> > Neither test execution order nor bundle build time are fixed, this makes it almost impossible why the OOM happens on Jenkins IMO. > > Not sure why do...

https://wiki.openjdk.org/display/wakefield/Pure+Wayland+toolkit+prototype is (hopefully) a prereq as SWT_AWT bridge relies on sun.awt.X11.XEmbeddedFrame which doesn't work under wayland for obvious reasons.

I have landed a generic safety net that happens to fix this case too. The snippet you created can serve as an example how to report issues in SWT ....

This complicates things IMO. As https://docs.gtk.org/gtk3/method.Widget.set_visible.html is available since Gtk 2.18 it should be valid to replace the calls to gtk_widget_show/hide with gtk_widget_set_visible and have things even clearer. Regarding the...

You can see how straightforward the c code is at https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/gtk/gtkwidget.c?ref_type=heads#L9091 so if you want to reduce deprecated usages please start replacing gtk_widget_hide/show with gtk_widget_set_visible.