Bug Report: Deterministic sequence leads to QCad crashing with a Segfault

[dpot]

Hi,

For some reason, I am unable to register for the bug tracker, so I am posting a bug report here.

The following deterministic sequence of interactions leads QCad (V3.32.2, Ubuntu 24.10) crashing with a segfault.

Since the sequence is rather involved, I've recorded a video: https://youtu.be/ctNVi538Bdg

1. Select Ordinate (X/Y)
2. Click the canvas
3. Click New
4. Select X/Y (from points)
5. Click the canvas
6. Select Vertical
7. Select the first canvas ("Untitled 1")
8. Click the canvas
9. Click the canvas at a different location
10. Select intersection manual
11. Select free
12. Click the canvas
13. Select Anti alias
14. Select the second canvas ("Untitled 2")
15. Click the canvas
16. Click the canvas at a different location
17. Select "Reset/Idle"
18 Click the canvas
19. Click print preview

QCad then crashes with the following backtrace:
Thread 1 "qcad-bin" received signal SIGSEGV, Segmentation fault.
0x00007ffff3e1696f in REcmaAction::getDocumentInterface (
context=0x7fff42800198, engine=0x555559164100)
at generated/REcmaAction.cpp:1033
1033 self->getDocumentInterface();
(gdb) bt
#0 0x00007ffff3e1696f in REcmaAction::getDocumentInterface
(context=0x7fff42800198, engine=0x555559164100)
at generated/REcmaAction.cpp:1033
#1 0x00007fffeefdccc3 in QScript::FunctionWrapper::proxyCall(QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::JSValue, QTJSC::ArgList const&) ()
at /home/guifuzz/Qt5.13.2/5.13.2/gcc_64/lib/libQt5Script.so.5
#2 0x00007fffeeef8ac8 in QTJSC::NativeFuncWrapper::operator()(QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::JSValue, QTJSC::ArgList const&) const ()
at /home/guifuzz/Qt5.13.2/5.13.2/gcc_64/lib/libQt5Script.so.5
#3 0x00007fffeeed337b in cti_op_call_NotJSFunction ()
at /home/guifuzz/Qt5.13.2/5.13.2/gcc_64/lib/libQt5Script.so.5
#4 0x00007fff4c237a4b in ??? ()
#5 0x0000000000000000 in ??? ()

[CVH]

Hi, and welcome to the QCAD forum.

Starting a tool in one drawing, hopping to another in between unfinished tools is not common practice.
At some point it seems like you are able to confuse the application big time.

The best place to report this untypical error is QCAD Bugtracker.
You need to have or apply for a account there what is unrelated to your forum account.

Regards,
CVH

[andrew]

Note that this is a self-compiled QCAD Community Edition, compiled against Qt version 5.13.2 which is not recommended and which we do not use here on Linux at all.