The log I generated yesterday is the same up to the point of your crash.
There are various bug reports with similar subject, example: https://gitlab.gnome.org/GNOME/gimp/-/issues/6802
The problem is no error messages. You could post a bug report on https://gitlab.gnome.org/GNOME/gimp/-/issues but do not hold your breath for a solution.
There are a couple gimp command line switches that you could try (invoke same as --verbose)
-------
--no-cpu-accel
Do not use special CPU acceleration functions. Useful for finding or disabling buggy accelerated hardware or functions.
-d, --no-data
Do not load patterns, gradients, palettes, or brushes. Often useful in non-interactive situations where start-up time is to be minimized.
------
Might get more info, otherwise
Clutching at straws, in case it is the latest Gimp, have you tried an earlier version, maybe Gimp 2.10.14 which was fairly stable.
Previous versions here: https://download.gimp.org/mirror/pub/gimp/v2.10/
There are various bug reports with similar subject, example: https://gitlab.gnome.org/GNOME/gimp/-/issues/6802
The problem is no error messages. You could post a bug report on https://gitlab.gnome.org/GNOME/gimp/-/issues but do not hold your breath for a solution.
There are a couple gimp command line switches that you could try (invoke same as --verbose)
-------
--no-cpu-accel
Do not use special CPU acceleration functions. Useful for finding or disabling buggy accelerated hardware or functions.
-d, --no-data
Do not load patterns, gradients, palettes, or brushes. Often useful in non-interactive situations where start-up time is to be minimized.
------
Might get more info, otherwise
Clutching at straws, in case it is the latest Gimp, have you tried an earlier version, maybe Gimp 2.10.14 which was fairly stable.
Previous versions here: https://download.gimp.org/mirror/pub/gimp/v2.10/