SU Unexpectedly Quit

I don’t use a Mac, but I understand that a working SketchUp 2021 (and/or MacOs 11) driver and plugin for 3D Connexion devices has not yet been released. A well behaving beta driver mentioned in another thread.

I tried various older versions, newer versions and the beta. The only driver that is somewhat usable on my system is 10.6.5.

I am still getting the random crash. Happened a few minutes ago, I sent the BugSplat report. Any advice? And this happened on Windows. So now, the problem is on both MacOS and Windows. And this is with two different SpaceNavigator devices. Thanks …

I have also seen this crash and reported it on the 3DConnexion forum. Time will tell whether they do anything about it…

The crash occurs with the latest Mac beta driver too. It is definitely still beta, with various bugs reported on the 3DC forum. It seems that nearly all of their attention is focused on figuring out how to pass modifier keys through to apps from their devices that have customizable buttons, and “lesser” bugs such as this are on hold.

I started a new file, thinking the previous one was corrupted. Another BugSplat, just sent. Cannot use SU with this problem. Very frustrating, hope this does not happen to others. :weary:

I’m a little late to this thread party, but regarding crashing when closing files, I’ve sent a slew of nastily commented bug splats recently because I’m at my wits’ end with SU2021. When I read the stack trace of the crashed threads in the Mac crash reporter, I see all kinds of wonky coding going on in the stack trace. I say this because you may be looking at the 3D Connexion drivers as the source of issues, but that may just be a red herring… I’ve had the closing of a file result in a crash in an NSColorWell drawing routine that has called into Ruby for some reason. And SU really doesn’t like files on a mounted network drive since I’ve seen crashes in the SketchUpModelReader which is C++ code called from Obj-C code. I feel like the coding team is cobbling things together from a mix of C, C++, Obj-C and Ruby code and not properly bridging between them. My 2 cents because I’m seriously pissed off at this current SU 2021 build.

1 Like

I am code illiterate (all languages). I have seen many posts titled, “SU Unexpectedly Quit”. There seem to be many unique factors involved. My files are not on a mounted network drive.

Since in my case, the crashes are completely random in nature, and therefore not reproducible, I am and probably will continue to be ignored.

I have been using the same SpaceNavigator hardware and driver in SU versions 2019 and 2020 without these crashes.

My only course of action is to continue submitting BugSplat reports.

Are you still on 10.11?

I’m on Catalina 10.15.

What extensions do you have ?
Are you running from the right location (ie the folder SketchUp 2021 in the application folder)?

The 15 bugsplats that you’ve sent in during the last three weeks have been for eight different reasons. More often when there are crashes it’s for the same reason each time.

I can’t take any good guesses about what would cause so many different issues, so I will ask the developers to take a look at the range of issues, and see if there is something in common.

To answer Mike’s question, you do appear to be running SketchUp from the right location.

The app is within its SketchUp 2021 folder at the root of the Applications folder. I’m not seeing anything related to permissions issues when reading the stack traces, so I’m fairly positive all is good there.

I have quite a few extensions, though. But the crashes I’m seeing most often don’t occur when invoking a function from a plug-in, but if they did, I’d certainly place blame on that author instead of the Trimble team :slight_smile: But to put some responsibility on the Trimble team, it isn’t a well architected app when an interpreted scripting environment can crash the hosting app.

Here’s a stack trace that exemplifies someone not doing their job on the coding team… If you follow the trace from the top of the run-loop downward (read in reverse order from line 41 up to line 0), you will see line 4 executing some sorting initialization method/function… The programmer has inserted an assert() catch for something that is out of the ordinary and not expected, but instead of handling the unexpected value or data, the app bails out. This is craptastic lack or error handling on that programmers part. They should catch the condition and either alert the user and go from there, or cancel whatever operation was committed that caused the problem and leave the app in a stable condition. To just fall-out and crash is really poor coding.

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff6fc1c33a __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff6fcd8e60 pthread_kill + 430
2 libsystem_c.dylib 0x00007fff6fba3808 abort + 120
3 libsystem_c.dylib 0x00007fff6fba2ac6 __assert_rtn + 314
4 com.sketchup.SketchUp.2021 0x0000000102762adb __gl_pqSortInit + 796
5 com.sketchup.SketchUp.2021 0x0000000102763bdf __gl_computeInterior + 319
6 com.sketchup.SketchUp.2021 0x00000001027681c9 gluTessEndPolygon + 166
7 com.sketchup.SketchUp.2021 0x000000010288b87a TesselatorImpl::Tesselate() + 40
8 com.sketchup.SketchUp.2021 0x00000001027ccffa CFaceTesselator::Tesselate(ISketchView*, bool, bool) + 684
9 com.sketchup.SketchUp.2021 0x00000001027249d5 sketchup::graphics::Tesselator::TesselateFace(CFace const*, sketchup::graphics::Primitivesketchup::graphics::PolygonVertex) + 127
10 com.sketchup.SketchUp.2021 0x0000000102724cd1 sketchup::graphics::Tesselator::TriangulateFace(CFace const
, sketchup::graphics::Primitivesketchup::graphics::PolygonVertex) + 73
11 com.sketchup.SketchUp.2021 0x0000000102717651 sketchup::graphics::FaceBuilder::TessellateFace(CFace const
, std::__1::vector<sketchup::graphics::FaceVertex, std::__1::allocatorsketchup::graphics::FaceVertex >) + 91
12 com.sketchup.SketchUp.2021 0x000000010271739d sketchup::graphics::FaceBuilder::BuildFaceGroupNode(std::__1::vector<CFace const
, std::__1::allocator<CFace const*> > const&, sketchup::graphics::FaceProperty const&, sketchup::graphics::FaceGroup*) const + 787
13 com.sketchup.SketchUp.2021 0x0000000102717019 sketchup::graphics::FaceBuilder::BuildNode(sketchup::graphics::FaceGroups*) const + 169
14 com.sketchup.SketchUp.2021 0x000000010271630d sketchup::graphics::ComponentBuilder::BuildNode(sketchup::graphics::ComponentNode*) + 813
15 com.sketchup.SketchUp.2021 0x000000010274ca5b sketchup::graphics::ComponentGraph::BuildComponentNode(CComponent const*) + 279
16 com.sketchup.SketchUp.2021 0x000000010274d27c sketchup::graphics::ComponentGraph::UpdateComponentNode(CComponent const*) + 86
17 com.sketchup.SketchUp.2021 0x000000010274cfab sketchup::graphics::ComponentGraph::UpdatePartial() + 315
18 com.sketchup.SketchUp.2021 0x000000010274ce03 sketchup::graphics::ComponentGraph::Update() + 53
19 com.sketchup.SketchUp.2021 0x0000000102719751 sketchup::graphics::ClassicRenderer::DrawFrame(sketchup::graphics::FrameInfo const&, atlast::geometry::CBoundingBox3d const&, atlast::utils::CColor const&, sketchup::graphics::IRenderer::ItemBufferDrawing) + 83
20 com.sketchup.SketchUp.2021 0x0000000102573b9f CSketchView::DrawEverything(bool, bool, unsigned int, sketchup::graphics::TiledFrameInfo const*) + 749
21 com.sketchup.SketchUp.2021 0x00000001025736b0 CSketchView::Draw(bool) + 636
22 com.sketchup.SketchUp.2021 0x0000000102332697 CMacSketchUpView::OnDraw() + 59
23 com.apple.AppKit 0x00007fff3335ef4b -[_NSOpenGLViewBackingLayer display] + 836
24 com.apple.QuartzCore 0x00007fff414f0e09 CA::Layer::display_if_needed(CA::Transaction*) + 757
25 com.apple.QuartzCore 0x00007fff414cf106 CA::Context::commit_transaction(CA::Transaction*, double) + 334
26 com.apple.QuartzCore 0x00007fff414cdcf0 CA::Transaction::commit() + 644
27 com.apple.AppKit 0x00007fff32dfdda1 __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 266
28 com.apple.AppKit 0x00007fff3351d080 ___NSRunLoopObserverCreateWithHandler_block_invoke + 41
29 com.apple.CoreFoundation 0x00007fff359ece15 CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 23
30 com.apple.CoreFoundation 0x00007fff359ecd47 __CFRunLoopDoObservers + 457
31 com.apple.CoreFoundation 0x00007fff359ec2e5 __CFRunLoopRun + 874
32 com.apple.CoreFoundation 0x00007fff359eb91e CFRunLoopRunSpecific + 462
33 com.apple.HIToolbox 0x00007fff34617abd RunCurrentEventLoopInMode + 292
34 com.apple.HIToolbox 0x00007fff346176f4 ReceiveNextEventCommon + 359
35 com.apple.HIToolbox 0x00007fff34617579 _BlockUntilNextEventMatchingListInModeWithFilter + 64
36 com.apple.AppKit 0x00007fff32c5e039 _DPSNextEvent + 883
37 com.apple.AppKit 0x00007fff32c5c880 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
38 com.apple.AppKit 0x00007fff32c4e58e -[NSApplication run] + 658
39 com.apple.AppKit 0x00007fff32c20396 NSApplicationMain + 777
40 com.sketchup.SketchUp.2021 0x000000010231d3de main + 147
41 libdyld.dylib 0x00007fff6fad4cc9 start + 1

Hi Colin. Yes, the “eight different reasons” (at least) has really fueled my frustrations, if you can’t already tell from my bug-splat comments :confused: It seems like the 21.0 release is full of problems because the various stack traces have very few similarities. I do, however, see Ruby more often than not at the top of the stack which is disconcerting.

My main point to begin with was, the 3D Connexion drivers may indeed be causing problems, but I’d scrutinize crash logs before pointing that finger because SU 21.0 crashes if you look at it wrong :confused:

Try looking at 2021 fondly, that might help.

The biggest change Ruby wise with 2021 is that it was updated to version 2.7. During a testing period none of the extension developers had any problems, but later on we found some that had problems with the change.

Anyway, I will see what the developers say about your comment about how invalid data is handled, and if any of them are brave enough to read your bugsplat reports.

Well, still no resolution. SU and 3Dx support have not provided any meaningful assistance. Yesterday I had 20-30 repeated crashes. This type of problem basically makes SU unusable.

Today, a more drastic, last ditch move. I have removed the 3D Space Navigator from the system and will NOT reinstall. Will do a clean install of MacOS (Mojave) and SU2019 ( Last stable version for me ). Will not reload any extensions. I have wasted countless hours dealing with SU instability/compatibility issues. Fingers crossed.

I now have a special appreciation for all the posts dealing with “SU Unexpectedly Quit”.

Keep us posted on the crashing frequency w/o space navigation running. For what it’s worth I’m running 20 and 21 on Mojave daily (with loads of extensions) and all are pretty rock solid. Hope you can get to the bottom of the problem.

I am investing way too much time in system/application administration. Namely, trying to determine what makes SU unstable in my environment. While trying to get back to a stable setup, I have created a completely generic SU environment. No SU extensions, no peripheral hardware devices (Space Navigator, Logitech mouse, etc.) no MacOS (Mojave) apps (only SU of course). Even reverted to SU 2019 (not perfect but, least glitchy). I am creating this “vanilla” setup on two computers, MacOS and Win10. I am using only new SU model files. Will have some results soon, I hope.

In the meantime, I am doing research on what variables (user, system, extensions, etc.) create instability in SU. I am finding large numbers of “crashes”. Just in these forums, a search with keywords, unexpectedly quit, crash, frozen, will not open, stopped working etc. generate extensive lists. And yes, many of these are user caused. And, yes, there are many users who testify to a “rock solid” SU experience. But many, like mine, go unanswered. And I also realize that the forums are administered, in large part, by un-paid volunteers who have limited resources.

Troubling are posts like @bergdesign (earlier in this thread) that seem not to arouse more interest. I have sent a large number of BugSplat reports. Am I naïve in thinking that the cause of repeated crashes could not be diagnosed through these reports? Is it possible that at least some of these crashes (mine and others) are related to the concerns voiced by @bergdesign?

What is your environment? What computer model and OS? Your profile is blocked for some reason which is not very helpful for anyone who wants to help you.

Another mystery, “profile blocked”. Just looked at my profile. Do I have the ability to block/unblock my profile?

I am trying desperately to get SU stable on the primary MacOS computer:

MacOS (Mojave)
iMac AMD Radeon R9 M395X 4 GB
16GB Ram, 1TB SSD
SU 2021, 2020, 2019
Reloaded MacOS (Mojave) and SU2019

I am also testing in parallel, a Windows machine:
Win10
Intel(R) Core™ i9-10900K CPU @ 3.70GHz
32GB Ram, 1 TB SSD
RTX 2060 Super

I could be wrong, but I doubt the issue is caused by hardware/OS. Both systems have fresh “vanilla” OS and SU installations. Additionally, I have PM’d @colin with many BugSplat reports.

1 Like