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.
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 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.
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 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
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.
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.