Crashing app when I change nr. of circle segments

If you need your tiny parts in modeling context with other parts, then make the tiny parts components. Make a copy of the component and place it off to the side somewhere. Scale up the copy and edit/tweak the large copy. The original-sized model will change with the edits in the large copy.

John, the crash dump I get shows a segment violation (i.e. bad address) in CVertex::CountEdges(), which to me seems to say that there is a bug in that function that is triggered because somehow the relationship between vertices and edges is messed up in that model. I don’t think it has anything to do with text input.

I’ve started the model from scratch several times. And the model is 2D and has a very simple geometry.

I got this, saying it came from the TextField, so I tried doing the change in ruby and it worked from there…

Application Specific Information:
Performing @selector(onNumberOfSegmentChanged:) from sender NSTextField 0x608000380ea0

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   ???                           	0x00007fff7ecaa118 OBJC_METACLASS_$_NSObject + 0
1   libCommonUtils.dylib          	0x000000011384f6ec CNotificationCenter::SendNotification(char const*, void*) + 188
2   com.sketchup.SketchUp.2015    	0x000000010eac59b4 CSelectionSet::AddElement(CDrawingElement*, bool) + 50
3   com.sketchup.SketchUp.2015    	0x000000010e8c3238 EdgeCmds::AddCurveToSelection(CCurve*) + 87
4   com.sketchup.SketchUp.2015    	0x000000010e8c3b75 EdgeCmds::SetCurveSegments(int, bool) + 250
5   com.sketchup.SketchUp.2015    	0x000000010e5ea431 0x10e572000 + 492593
6   libsystem_trace.dylib         	0x00007fff8ed49cd7 _os_activity_initiate + 75
7   com.apple.AppKit              	0x00007fff93920eb1 -[NSApplication sendAction:to:from:] + 452
8   com.apple.AppKit              	0x00007fff93936946 -[NSControl sendAction:to:] + 86
9   com.apple.AppKit              	0x00007fff93973471 -[NSTextField textDidEndEditing:] + 487

Very strange! All the crashes I have gotten were from that same segment violation I reported.

Edit: I managed to get a crash like the one you report. The common feature is starting with EdgeCmds::AddCurveToSelection, but this crash and the other one follow different sequences after that, suggesting that the manner of selecting the curve may matter? (This topic is probably getting too technical for the forum - maybe we should wait for someone from Trimble to chime in)

Check your Apple User Diagnostic Report, not BugSplat…
does it show the same as mine?
john

This is not my area of expertise, but for other SU’ers reference, slbaumgartner’s crash is id 66587.