<!-- See our full bug reporting guidelines at https://inkscape.org/contribute/report-bugs/ Writing a good bug report will ensure we'll be able to help efficiently. 🙂 --> #### Summary: <!-- Summarize the issue/suggestion concisely: --> Inkscape 1.4 (e7c3feb100, 2024-10-09) on Linux becomes not responsive (crashes), when working with the attached SVG file. The SVG file was created on Windows 10, using Inkscape. #### Steps to reproduce: <!-- Describe what you did (step-by-step) so we can reproduce: --> - open Inkscape - Load the .svg file. - Try to access path _path-1-37_. #### What happened? It seems the problematic path is _path-1-37_. Everytime I access that path, the load on the machine spikes and Inkscape no longer responds to input. Once or twice the machine has recovered after a few minutes, many times it did not and I simply had to Force Quit the application. #### What should have happened? The load on the machine should not spike and the program should remain usable. I should not need to force quit the application! #### Sample attachments: <!-- Attach the sample file(s) highlighting the issue, if appropriate. --> [image0.svg](/uploads/c456fe7511f909febbb9ff0ce608498e/image0.svg) #### Version info <!-- Open 'Help > About' and click on the little bug icon in the bottom right corner that copies the debug information to your clipboard. For command line users, run 'inkscape --debug-info'. For Inkscape 1.0.2 and older, please manually add the Inkscape Version and Operating System Version. The Inkscape version is listed in the About dialog. For command line users, run 'inkscape -V' Paste the information in the empty space between the apostrophes below: --> ``` Inkscape 1.4 (e7c3feb100, 2024-10-09) Compile (Run) GLib version: 2.82.0 GTK version: 3.24.43 (3.24.43) glibmm version: 2.66.1 gtkmm version: 3.24.5 libxml2 version: 2.13.4 libxslt version: 1.1.42 Cairo version: 1.18.2 (1.18.2) Pango version: 1.54.0 (1.54.0) HarfBuzz version: 9.0.0 (9.0.0) OS version: GNOME 47 (Flatpak runtime) ``` <!-- ❤️ Thank you for filling in a new bug report, we appreciate the help! ❤️ Please be patient while we try to find the time to look into your issue. Remember that Inkscape is developed by volunteers in their spare time, we'll try our best to respond to all reports. --> <!-- Please be careful when/after writing # for example in logs, code, or versions of linux - use inline code span - single backticks (`) before and after it, like this - `#1618` - use multi-line code block - triple backticks (```) to fence/enclose console logs - attach long logs as a text file. --> #### Logs Herewith an extract of my syslog log file on my system when a crash happens. [Inkscape_syslog.txt](/uploads/81128330a96ac24f39fc2c038086c014/Inkscape_syslog.txt)