Autoroute crashes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Deleted all traces that were autorouted before
2. Run autorouter for 100 rounds
3. Autorouter crashes after the 100th round is run and next phase of 
autorouting starts (not sure what's its name)

I believe the problem started once I deleted all the pre-autorouted traces and 
vias and tried to re-run autoroute. I could be wrong. I have been working on 
this file for some days before and autorouting was not crashing fritzing

Attach your sketch file and/or custom part files to the bug report.

What is the expected output? What do you see instead?
...(loads of similar debugging msgs before)
"routing net 16, subnets 2, traces 1, routed 1" 
"routing net 17, subnets 2, traces 1, routed 1" 
"routing net 18, subnets 3, traces 1, routed 1" 
"routing net 20, subnets 5, traces 0, routed 0" 
"routing net 21, subnets 2, traces 0, routed 0" 
"routing net 22, subnets 5, traces 0, routed 0" 
"traceback zero points" 
"traceback zero points" 
"overlap not found" 
"overlap not found" 
"missing source connector" 
Segmentation fault

What version of Fritzing are you using? On what operating system?
0.7.12 (b6882 2013-02-13) [Qt 4.8.3] on Linux Mint 13
also tried it
fritzing.2013.02.25.pc.zip on WinXP 32bit
and confirmed same issue is present

Please provide any additional information below.

Original issue reported on code.google.com by georgeko...@gmail.com on 19 May 2013 at 11:08

Attachments:

• v1.fzz

[GoogleCodeExporter]

Tested on windows, with version 0.7.12 and 0.7.13. Neither crashes, though 
0.7.13 (unreleased) finds a solution and 0.7.12 stops at 100.

Will test under linux.

Original comment by irasc...@gmail.com on 20 May 2013 at 5:09

[GoogleCodeExporter]

Same behavior under Ubuntu 12.04, 32-bit: under 0.7.12 routing stops at 100 
rounds, chooses best result so far, but doesn't crash. Tried deleting the few 
traces that were left first, also tried routing the file as-is. With 0.7.13 
autorouter finishes routing at 45 rounds, no crash.

Not sure what to suggest from here except to wait for the next release?

Original comment by irasc...@gmail.com on 20 May 2013 at 5:34

[GoogleCodeExporter]

sorry for the late reply and thank you so much for the support!
My last 2 tests were from the same machine (dual boot PC).
Tried it from Windows server 2013 on a different machine and worked fine. Could 
it be a graphics (NVidia) card dependent problem??? Long shot but hey...

Original comment by georgeko...@gmail.com on 20 May 2013 at 8:45

[GoogleCodeExporter]

Can't completely rule out the graphics card idea, but I agree it's a long-shot. 
Another long shot would be resources--that phase of cleaning up after the 
autorouter creates a whole lot of objects--you could take a look at a 
cpu/memory/disk monitor to see whether you are getting pinned. Sorry I don't 
have a better answer.

Original comment by irasc...@gmail.com on 21 May 2013 at 3:50

• Changed state: UnableToReplicate
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Thats strange :) I tried today running it and monitoring CPU/disk/RAM and only 
CPU got up to 88% but not any higher during tracing and autorouting completed 
successfully.
Moved a component on the board, re-run autorouting and BAM! segmentation fault.
Im gonna be asking friends to do the autorouting for me until a new release is 
out :)
Thanks again

Original comment by georgeko...@gmail.com on 21 May 2013 at 9:20

[GoogleCodeExporter]

I'll try moving a component and see if I can get the error.

Original comment by irasc...@gmail.com on 21 May 2013 at 4:44

[GoogleCodeExporter]

Issue has moved to new issue tracker at github. Please continue the discussion 
at https://github.com/fritzing/fritzing-app/issues

Original comment by andre.knoerig@gmail.com on 23 Sep 2014 at 3:40

• Changed state: ToGithub