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
I encountered a problem when migrating from version 3.3.1 to 3.3.3. Methods NFD_PickFolder, NFD_OpenDialog, NFD_OpenDialogMultiple, NFD_SaveDialog stopped working and crashes with error. I saw the recording in nfd_gtk.cpp file. Note: We do not check for malloc failure on Linux - Linux overcommits memory!
On a system with Windows 10, everything works well and the dialog windows open correctly. Can you please clarify is that problem on API side or am I doing something wrong? And if this is a problem on the api side can you suggest a workaround?
Stacktrace or crash log output
(process:6228): Gtk-CRITICAL **: 12:02:41.770: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
# A fatal error has been detected by the Java Runtime Environment:
#
(process:6228): Gtk-CRITICAL **: 12:02:41.770: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
# SIGSEGV (0xb) at pc=0x00007f509258ccf4, pid=6228, tid=6229
#
(process:6228): Gtk-CRITICAL **: 12:02:41.770: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
The text was updated successfully, but these errors were encountered:
Version
3.3.3
Platform
Linux x64 - Ubuntu 22.04.3
JDK
17.0.5
Module
NFD
Bug description
I encountered a problem when migrating from version 3.3.1 to 3.3.3. Methods
NFD_PickFolder
,NFD_OpenDialog
,NFD_OpenDialogMultiple
,NFD_SaveDialog
stopped working and crashes with error. I saw the recording innfd_gtk.cpp
file.Note: We do not check for malloc failure on Linux - Linux overcommits memory!
On a system with Windows 10, everything works well and the dialog windows open correctly. Can you please clarify is that problem on API side or am I doing something wrong? And if this is a problem on the api side can you suggest a workaround?
Stacktrace or crash log output
The text was updated successfully, but these errors were encountered: