davidperrenoud
commented
10 years ago From irasc...@gmail.com on March 02, 2009 01:24:24
This is the old loop example, and not the most recent. I've attached the file. The bug turns out to be a difficult one, and luckily not related to autorouting. You can get the crash simply by opening the file and then immediately deleting the tracewire "wire59".
It's crashing in QGraphicsSceneFindItemBspTreeVisitor::visit because one of the QGraphicsItems that is in its list has been deleted. The bug survives if you open the file, do a save-as, load the new file, and delete wire59 from there. Wire59 is chained to several other wires, and you get the crash if you delete any of the others--it is one of these other wires that is incorrectly remaining on QGraphicsSceneFindItemBspTreeVisitor's list. You don't get the crash if you move all of the chained wires out from under another set of traces, but I don't know whether the "beneathness" is a source of the problem. Interestingly, if you move all the wires, then undo so they're back in the original position, you get the crash again.
When trying to find similar bugs out on the web, the advice was to call PrepareGeometryChange() whenever the boundingrect of a GraphicsItem changes. However, as far as I can tell, wires and connector items are pretty diligent about doing so. But maybe it's one of the parts that the wires are beneath? I guess this is also worth checking.
Attachment: Loopcopy.fz
From irasc...@gmail.com on February 26, 2009 11:59:24
open the digital/loop example. hit autoroute and let it finish. then undo autoroute. fritzing crashes.
Original issue: http://code.google.com/p/fritzing/issues/detail?id=605