Fritzing (0.96 version) crashes when exporting gerber file

[Jakenzhu]

Fritzing 0.96 version crashes everytime when exporting gerber file, no matter under Mac OS, Window or Ubuntu.
Crash error information is as below, how to solve it?

Process:
Path:
Identifier: Version:
Code Type: Parent Process: Responsible: User ID:
Fritzing [901] /Applications/Fritzing.app/Contents/MacOS/Fritzing org.fritzing.Fritzing
0.9.6 (bda4e) X86-64 (Native)
??? [1] Fritzing [901]
501
Date/Time:
OS Version: Report Version: Bridge OS Version: Anonymous UUID:
2021-07-22 17:59:20.561 +0800 macOS 11.5 (20G71)
12
5.5 (18P4759a)
9CDB1722-8037-C840-DD29-74FDA88846BE
Time Awake Since Boot: 2000 seconds System Integrity Protection: enabled
Crashed Thread:
Exception Type: Exception Codes: Exception Note:
Termination Signal: Termination Reason: Terminating Process:
0 Dispatch queue: com.apple.main-thread
EXC_BAD_ACCESS (SIGSEGV) KERN_INVALID_ADDRESS at 0x0000000000000010
EXC_CORPSE_NOTIFY
Segmentation fault: 11 Namespace SIGNAL, Code 0xb exc handler [901]
VM Regions Near 0x10: →
__TEXT Applications/Fritzing.app/Contents/MacOS/Fritzing
1002b5000-100b0d000 [ 8544K] r-x/r-x SM=COW /
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.qt-project.QtCore 0x0000000101c4e84e QString::toDouble(bool*) const + 30 1 org.fritzing.Fritzing 0x00000001003ff5ab SVG2gerber::doPoly(QDomElement&, SVG2gerber::ForWhy, bool, QHash<QString, QString>&, QString&, int&) + 315
2 org.fritzing.Fritzing 0x00000001003fc9e2 SVG2gerber::allPaths2gerber(SVG2gerber::ForWhy) + 19298
3 org.fritzing.Fritzing 0x00000001003f67aa SVG2gerber::renderGerber(bool, QString const&, SVG2gerber::ForWhy) + 1162

[vanepp]

Post the sketch (the .fzz file) here (upload is 7th icon from the left in the reply menu) and one of us will have a look at the issue. The most likely cause is a badly configured part.

Peter

[Jakenzhu]

Pls take a look of the uploaded file.
relay-led-motor-V2_2_gnd_2switch_V1.fzz (56.7 KB)

[vanepp]

Gerber dies for me too. It looks like one or both of the custom parts are incorrect, I’ll have a look and see if I can correct them. DRC is reporting overlaps which likely means incorrectly configured parts:

edit1:

To my surprise it isn’t the user supplied parts (although both are wrong) but the Q4 sot23 transistor from core parts (I don’t yet know why). I deleted all traces and most of the parts (leaving the holes and vias) verified it would export as a gerber, then added the parts back in one by one by undoing the deletes one at a time then doing the gerber export until it broke at Q4. This sketch (with Q4) breaks in gerber export:

with Q4 removed it exports successfully. I’ll have a look at the part and see if I can see why it is breaking.

the sketch the above two images were created from so you can try it for yourself. This sketch should die in gerber export, deleting Q4 fixes that.

relay-led-motor-V2_2_gnd_2switch_V2.fzz (5.6 KB)

edit2: A workaround (this appears to be a Fritzing bug which I will report!) If you change the rotation of Q4 from 180 to 179 gerber export then works:

That still leaves the part errors though. For the esp32, replacing the current par with this one should fix things up:

ESP-WROOM-32 (ESP-32S) part

Unfortunately there was more wrong than just the scaling. Some of the pins in schematic were also wrong (likely due to the pins not being in sequence) and the grounds weren’t bussed. In the end I renumbered the pins as that was easier than trying to figure out the current scheme and cleaned up schematic and changed a couple of pins that don’'t match the current data sheet on the manufacturer’s site. edit: replaced by a new part posted below. Peter

Here is a fixed copy of the other custom part. The current one lacks a copper1 layer in pcb among other faults. The moduleId is the same so you will need to delete the current part (and shutdown and restart fritzing to really delete it) before you can load this one.

DC 5V to 3.3V DC-DC Step-Down Power Supply Buck Module AMS1117 LDO 800MA-fixed.fzpz (6.6 KB)

Some of your vias are overlapping parts. This will work fine usually, but will cause DRC to complain.

Peter

[vanepp]

This has been fixed (or at least no longer occurs ) in 0.9.7. I closed the ticket on github so if it reoccurs we need to open a new ticket (I don’t think it the bug was fixed specifically in 0.9.7, it just no longer occurs on 0.9.7 so the trigger value may have changed from 180 degrees!)

Peter