is the process still active when you get the issue? it would be useful to get a backtrace of those warnings with the dbgsym installed, you can attach to a working instance to get it
$ gdb -p <pid>
(gdb) b g_log
(gdb) c
it might stop on debug prints in which case you can keep doing "c" but should also get the warning and then you can get the bt
is the process still active when you get the issue? it would be useful to get a backtrace of those warnings with the dbgsym installed, you can attach to a working instance to get it
$ gdb -p <pid>
(gdb) b g_log
(gdb) c
it might stop on debug prints in which case you can keep doing "c" but should also get the warning and then you can get the bt