I analyzed the problem and found out, that it does not seem to be a problem with the images I try to open.
The problem seems to be a complex SVG file that got visited when I browse to the destination directory of the image.
I checked the debugger output of gdb and I saw, that nautilus start a new thread whenever I visit the directory with this SVG file. But because this SVG file is really complex, this thread doesn't terminate in an apropriate time. When I open another image without this thread to be terminated, nautilus hangs...
(Perhaps, because it waits for a lock to be released by the thread that creates the SVG preview)
Unfortunately I can't disclose this SVG file by now. But it is apparently very complex - Inkscape needs a lot of memory and time to render it. So perhaps the SVG thumbnailing mechanism of nautilus has to be prevented to thumbnail complex images...
I analyzed the problem and found out, that it does not seem to be a problem with the images I try to open.
The problem seems to be a complex SVG file that got visited when I browse to the destination directory of the image.
I checked the debugger output of gdb and I saw, that nautilus start a new thread whenever I visit the directory with this SVG file. But because this SVG file is really complex, this thread doesn't terminate in an apropriate time. When I open another image without this thread to be terminated, nautilus hangs...
(Perhaps, because it waits for a lock to be released by the thread that creates the SVG preview)
Unfortunately I can't disclose this SVG file by now. But it is apparently very complex - Inkscape needs a lot of memory and time to render it. So perhaps the SVG thumbnailing mechanism of nautilus has to be prevented to thumbnail complex images...