I think the template was not saved as a "plain SVG" from Inkscape. In case someone else ends up with 9 pages of drawings before realizing the issue, here was my workaround: Unzip project with Tools->Project Utility Open each template .svg file in Inkscape and Save As "Plain SVG"...

I ended up here only after I think I figured out the culprit... I'm using Template A3_Landscape_ISO7200_Pep.svg . In my quick sampling of templates, this is the only TechDraw template that seems to cause bad SVG output issue. I think the template was not saved as a "plain SVG" from Inkscap...

And I suspect I've seen this in more places in the past few years: usually when moving stuff in tree view among 'group's and 'part's, a crash. With a normal release build it is very difficult to catch this kind of errors. I'm not claiming consistently-repeatable crashes. Just as you'd expect: the o...

When using the above build the whole issue can be reduced to a three-liner: And I suspect I've seen this in more places in the past few years: usually when moving stuff in tree view among 'group's and 'part's, a crash. I don't get to dig in often. I'm usually using FreeCAD under pressure to get a d...

I was able to reproduce on 0.20 weekly build pretty easily. I opened a bug. 4823 Anyone who can reproduce, especially in more "popular" Linux and Windows should add a crash report to support it. I would consider any crash with tip of the backtrace showing these two (and may be libc more re...

FWIW, @realthunder and @wwmayer are in the 'blame' for these lines. It looks like the method got there as part of a refactor. I'm not sure what other history it has. They may be the best equipped to understand the implications and how to fix it so that condition in the note never happens. It's too l...

have you any insight in what I could do to avoid this? Do you think is it related to the wb or FC or the graphic drivers? If this is the problem, I think the blame lies deep in FreeCAD. It should be fixed by someone familiar with the whole stack. The fix may come at the expense of performance (base...

Wow. It's tough to figure out where the CPU is in a large project with limited symbols. No source lines (that I could find) in the released binary, so I was looking in the wrong area for a long time. It doesn't help that I haven't touched x86 assembly in decades, or that I don't use lldb much. Looki...

I will try to figure out the differences of the two systems I suspect you are barking up the wrong tree. The behavior we both reproduced makes me think there is one of those memory usage bugs here. Stuff like use after free, buffer overflows, uninitialized memory. You said you were going to Try bui...

My (old) case started crashing when I tried importing tracks.