Comment 6 for bug 135650

Revision history for this message
C.Kontros (coryisatm) wrote :

Sebastien Bacher: "the log seems to be truncated and has no error, did you get the crash during this run?"

No. That was the output of the log. I'll do another. Like I mentioned on IRC, I couldn't get it to crash launching it with:

"G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gimp"

It went VERY slow that was it. I can make it crash if I create a new image or resize _ANYTHING_. Canvas, layer or image. This happens when launching it from the menu or via CLI.

Attached is another log where things work other than being slow. There's a difference somewhere. I just can't track it down. ion_ on #ubuntu-devel is having this same issue.