dnrops
/
gimp
mirror of https://github.com/GNOME/gimp.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Revert "Issue #7539: Opening some images lock GIMP." 

This reverts commit 9b94e347bc.

I leave a comment though, because we are not 100% sure that the issue is
gone. In fact, the upstream report is still opened.

The good point is that on stable code, we only debug crashes by default,
while the specific hang we had was happening with debugging metadata
warnings. So hopefully we won't have random people reporting GIMP
hanging (only people explicitly trying to help debugging GIMP).
This commit is contained in:
Jehan 2025-01-15 01:41:21 +01:00
parent b6fb472ae2
commit 135935c448
1 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
libgimpbase/gimputils.c
View File

@ -1317,16 +1317,12 @@ gimp_stack_trace_print (const gchar *prog_name,
/* Child process. */ /* Child process. */
gchar *args[9] = { "gdb", "-batch", gchar *args[9] = { "gdb", "-batch",
"-ex", "info threads", "-ex", "info threads",
/* We used to be able to ask for the full /* A bug, possibly in gdb, could lock the whole
* backtrace of all threads, but a bug, * GIMP process with a full thread backtrace in
* possibly in gdb, could lock the whole GIMP * some conditions. We aren't sure if it still
* process. So for now, let's just have a * exists. See issue #7539.
* backtrace of the main process (most bugs
* happen here anyway).
* See issue #7539.
*/ */
/*"-ex", "thread apply all backtrace full",*/ "-ex", "thread apply all backtrace full",
"-ex", "backtrace full",
(gchar *) prog_name, NULL, NULL }; (gchar *) prog_name, NULL, NULL };
if (prog_name == NULL) if (prog_name == NULL)