QCAD Bugtracker

Hi,

I have a nice minimally reproducible bug on QCAD v3.7.4 on Mac OS X 10.9.5 (Mavericks).
QCAD will segfault whenever I take the following steps:

1. Open a new document
2. Create a leader object (D,E) in the default ‘0’ layer. Leave its style and color defined by the layer, as per default.
3. Create a new layer, with a non-default line style or color. The line weight & layer name do not matter.
4. Select the leader object previously create
5. Open the property editor and assign the object to the new layer just created.
Every time, this will cause QCAD to segfault on my machine. The crash report is attached.

Another minimally reproducible path to the same error is to do the following:
1. Open a new document
2. Create a leader object (D,E) in the default ‘0’ layer. Give it a custom color and line style that over-ride the layer defaults.
3. Create a new layer, with a non-default line style or color. The line weight & layer name do not matter.
4. Select the leader object previously created.
5. Open the property editor and assign the object to the new layer just created.
6. Still in the property editor, switch the leader object’s color back to ‘By Layer’.
The same segfault will occur.

It seems that the crash is triggered by the action of changing a leader object’s color (and/or line style) in a manner that requires the object to check the containing layer’s default color and style. You can achieve this by either changing the object’s layer, or switching the color and style from being custom defined to ‘by layer’, as long as the selection requires the line’s appearance to change.

Any thoughts? My machine’s crash report is attached.

Dan

When multiple superscripts or subscripts are used in a text field, re-opening the saved dxf file will fail to render all but the first super/subscript element. As per attached example. Bug occurs on all Mac OS X from Mavericks onward.

Minimal reproducible steps:
1. Open new document in QCAD
2. Add a text object
3. Make part of the text sub or super-script
4. Make another part of the text also sub/superscript, with at least one ‘normal’ character between the two sub/superscripts
5. Save file and close it. Don’t have to quit QCAD.
6. Reopen the file. Voila, all but the first sub/superscript element is broken.

Dan.

ps. QCAD is a pretty great piece of software, nice work all.

Since updating to QCAD 3.16 on MacOS, my dimension font face suddenly changed to something very unattractive and I can’t figure out how to reset it. I tried deleting QCAD and all references to it in ~/Library and then reinstalling, but no luck. Something weird has gone wrong with QCAD’s fonts.

The font change has made it impossible to open and redraw many DXF files because the new font face is larger and wider spaced and it ruins the layout of many documents.

Attached is an example of what the same DXF file looked like in the prior QCAD version, and the new version. No change to the DXF file.

Dan.

Hi,

I have just updated my Mac OS from 10.9.2 to 10.9.4. QCAD 3.6.2 seems to be working normally under the newest version of Mac OS, but has developed a very specific bug which leads to reproducible crashes when a text object is edited.

Steps to minimally reproduce:
1. Open QCAD
2. Create a text object
3. Place the text object on the canvas
4. double-click the text object and edit its contents
5. click OK to accept changes
6. repeat from step 4 three or four times.

After several attempts to edit a text object, QCAD will crash with EXC_BAD_ACCESS (SIGBUS) in thread 0 (QCoreApplication).
The crash can also be triggered by moving the text object around on the canvas (instead of editing its contents).
The bug does not require anything else (no other objects on the canvas, no particular font, occurs in both new and previously saved documents).

Apart from this bug, QCAD seems to work fine on OS X 10.9. The text editing crash did not occur before the latest OS update. No other applications on my system seem to be having any problems. If this problem can be fixed, I think QCAD will be quite usable on 10.9.

See also related bugs in:
 FS#1091