Investigating this some more, it seems that my initial report was inaccurate/misleading: The bug I'm seeing is bug #756868 <mailto:[email protected]>: the crash is caused by thumbnailing a large image file, which is by accident contained in that folder. I can reproduce a crash with just the image alone, and cannot reproduce without.
Thus: duplicate of #756868 <mailto:[email protected]>. Sorry for the spam, will check better next time. ~Mike On Sun, 05 Feb 2017 11:20:11 +0100 Mike Grunweg <[email protected]> wrote: > Package: nautilus > Version: 3.14.1-2 > Severity: important > Tags: lfs > > Dear Maintainer, > > * What led up to the situation? > trying to rename a large file saved on my hard disc > * What exactly did you do (or not do) that was effective (or > ineffective)? > Open a new nautilus window and navigate to the the file's containing folder. > Right-click the file, select "rename" from the Hamburger menu. > Start typing in the new name. > * What was the outcome of this action? > While typing in the new file name, nautilus crashes. > This usually takes a few seconds to happen. > * What outcome did you expect instead? > I can type in the new file name and rename the file. > > Extra information: > -I have experienced this with multiple files; it appears to me that the sole > cause of this the mere file size. This doesn't seem limited to renaming, > but also happens when selecting files. > -I can always reproduce it with the following file, the video from > https://air.mozilla.org/rust-paris-meetup-35-2017-01-19/: > Go to the download tab, download the mpeg4 version (650MB) and keep the default > name mp4.mp4. I then tried to rename it to something like > "Rust_meetup_Paris-2017-01.mp4", by the time I'm typing the year, nautilus crashes. > > Guessed cause: Memory access error > Opening a new nautilus instance per terminal and then doing the above yields an error message > "Speicherzugriffsfehler" upon crash. Executing |valgrind nautilus| yields the following log, > indicating an out-of-range memory access and that the process was killed. > > $ valgrind nautilus > ==2945== Memcheck, a memory error detector > ==2945== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. > ==2945== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info > ==2945== Command: nautilus > ==2945== > > (nautilus:2945): Gtk-WARNING **: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client > ==2945== Warning: set address range perms: large range [0x3a04c040, 0xc8c73884) (undefined) > ==2945== Thread 7: > ==2945== Invalid read of size 1 > ==2945== at 0x7525B30: ??? (in /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.3100.1) > ==2945== by 0x75274D5: ??? (in /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.3100.1) > ==2945== by 0x7527BE3: ??? (in /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.3100.1) > ==2945== by 0x751F818: gdk_pixbuf_scale (in /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.3100.1) > ==2945== by 0x751FDD5: gdk_pixbuf_scale_simple (in /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.3100.1) > ==2945== by 0x752115C: ??? (in /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.3100.1) > ==2945== by 0x547C159: ??? (in /usr/lib/libgnome-desktop-3.so.10.0.0) > ==2945== by 0x547C661: gnome_desktop_thumbnail_factory_generate_thumbnail (in /usr/lib/libgnome-desktop-3.so.10.0.0) > ==2945== by 0x4CB60F: ??? (in /usr/bin/nautilus) > ==2945== by 0x8AC2063: start_thread (pthread_create.c:309) > ==2945== by 0x8DBF62C: clone (clone.S:111) > ==2945== Address 0xffffffffba467a3b is not stack'd, malloc'd or (recently) free'd > ==2945== > ==2945==
