Nautilus seg fault in folder with javascript file

Opening a folder containing a javascript file generates a seg fault. To trigger this, I put a file foo.js containing just // or /* in an empty folder and open that folder in nautilus. The same happens when I have the folder opened in nautilus first and then move/create the file into that folder, or editing an existing file.

The strings // or /* has to be at the beginning of the file and the file name must end with .js.

It looks like libgio entered an infinite recursion: the core dump says

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f881e040bad in ?? () from /lib/x86_64-linux-gnu/
#1  0x00007f881e040fb8 in ?? () from /lib/x86_64-linux-gnu/
#2  0x00007f881e0411f3 in ?? () from /lib/x86_64-linux-gnu/
#3  0x00007f881e0411f3 in ?? () from /lib/x86_64-linux-gnu/
<omitted between>
#87223 0x00007f881e0411f3 in ?? () from /lib/x86_64-linux-gnu/
#87224 0x00007f881e0411f3 in ?? () from /lib/x86_64-linux-gnu/
#87225 0x00007f881dfcf1c5 in g_content_type_guess () from /lib/x86_64-linux-gnu/
#87226 0x00007f881e0369cd in ?? () from /lib/x86_64-linux-gnu/
#87227 0x00007f881e036e0b in ?? () from /lib/x86_64-linux-gnu/
#87228 0x00007f881e033095 in ?? () from /lib/x86_64-linux-gnu/
#87229 0x00007f881df6ad80 in ?? () from /lib/x86_64-linux-gnu/
#87230 0x00007f881dfb1194 in ?? () from /lib/x86_64-linux-gnu/
#87231 0x00007f881ec9f6b4 in ?? () from /lib/x86_64-linux-gnu/
#87232 0x00007f881ec9ca51 in ?? () from /lib/x86_64-linux-gnu/
#87233 0x00007f881d894ac3 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#87234 0x00007f881d926850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Version of nautilus is GNOME nautilus 42.6.

Likely unrelated, nautilus outputs the following in the terminal at startup, even when opening directories not causing the crash

(org.gnome.Nautilus:45165): Tracker-WARNING **: 16:28:58.848: Could not delete '.meta.isrunning': No such file or directory

** (org.gnome.Nautilus:45165): WARNING **: 16:28:58.848: Unable to initialize tag manager: Database version is too new: got version 28, but 26 is needed

Hi. Thanks for taking the time to report this issue. Unfortunately, the stack trace is missing some symbols (those “??”) that are needed to solve the problem, and this will make it hard for the developers to fix that crash. Please see stack traces for more information on how to provide a stack trace. Thanks in advance!

Also, please file the bug at Issues · GNOME / GLib · GitLab

Thank you @antoniof. I have filed an issue at seg fault due to infinite recursion (#3273) · Issues · GNOME / GLib · GitLab

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.