You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Main known issue is related to disposed but not finalized widgets, which would happen when e.g. their surrounding window is closed. Calling anything on such widgets might crash or do whatever, and this is design constraint in GTK.
This also effects GTK4, but probably nothing apart from GTK as it's AFAIK the only library calling g_object_run_dispose() explicitly at specific times. It might also affect other GObject libraries if used together with a GC'd language binding in the same process but it's not entirely clear if the problems actually happen there in practice.
Main known issue is related to disposed but not finalized widgets, which would happen when e.g. their surrounding window is closed. Calling anything on such widgets might crash or do whatever, and this is design constraint in GTK.
See https://gitlab.gnome.org/GNOME/gtk/-/issues/3711 for details.
This also effects GTK4, but probably nothing apart from GTK as it's AFAIK the only library calling
g_object_run_dispose()
explicitly at specific times. It might also affect other GObject libraries if used together with a GC'd language binding in the same process but it's not entirely clear if the problems actually happen there in practice.CC @bilelmoussaoui
The text was updated successfully, but these errors were encountered: