GNOME Bugzilla – Bug 771109
batch rename: crash if user types too fast
Last modified: 2016-09-16 07:38:36 UTC
Created attachment 335168 [details] Backtrace If the user inserts text to replacement text very fast, Nautilus may crash. How to reproduce: 1. Create several files: touch {0000..9999}.txt 2. Select any two files -> Rename -> "Find and Replace text" 3. type text as fast as possible. Nautilus may segfault here. This doesn't happen always though. Before testing, killall Nautilus instances, and test in a freshly opened instance. This happens mostly when the deselected file list is too big. Though the attached backtrace says "corrupted double-linked list," I get different reasons on different crashes.
I believe this is fixed since the last refactoring we did, which uses GTask and cancellables appropiately. https://git.gnome.org/browse/nautilus/commit/?id=66693775d91eb8278bc7f9d0c5674cdccbc3dd0b
Still present in master. Reopening.
In Nautilus files/folder search, If I type too fast, it seems like the search is delayed until the typing is complete (ie, when nautilus receives no more characters for certain time, probably some few milliseconds). But in batch renaming, the searching begins as soon as the first character is typed. This may be a way for the fix, if not done already. Thank you.
You mean in Search & Replace? I cannot manage to reproduce
I can also reproduce by keeping on pressing any single key on keyboard, or by copying some text, and paste by keeping on pressing C-v
same as 771129, we are freeing after free somewhere *** This bug has been marked as a duplicate of bug 771129 ***