<AWT Dev>  Review request for 8048289 Gtk: call to UIManager.getSystemLookAndFeelClassName() leads to crash
alexander.zvegintsev at oracle.com
Thu Jul 17 15:02:15 UTC 2014
You are right: UNIXToolkit.unload_gtk() is never called. But it will not
crash if we call it, somehow gtk-init-check() call allows to avoid crash.
However I want to leave this fix as simple as it is now, since
gdk_threads_init() should be called prior to gtk_init_check(),
and it is unnecessaryfor a simple version check.
On 07/17/2014 04:15 PM, Sergey Bylokhov wrote:
> Hi, Alexander.
> As far as I remember, we have a code, which closes this lib for the
> usual usage of gtk look and feel. Looks like we never call it, but if
> we call it it will cause the same crash? Can you investigate that?
> On 7/16/14 8:56 PM, Alexander Zvegintsev wrote:
>> Hello AWT team,
>> please review the fix
>> for the issue
>> UIManager.getSystemLookAndFeelClassName() calls
>> which loads gtk library, checks version, and closes library. Thread
>> specific data key is created upon gtk dlopen,
>> but this key is not deleted at dlclose. This produces a crash at
>> thread termination.
>> So this fix is a workaround for the glib issue , it simply doesn't
>> close library.
>> Simple case to reproduce this issue written on C is attached to .
>>  https://bugzilla.gnome.org/show_bug.cgi?id=733065
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the awt-dev