Closed GoogleCodeExporter closed 9 years ago
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
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
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
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
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
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
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
Original issue reported on code.google.com by
georgeko...@gmail.com
on 19 May 2013 at 11:08Attachments: