There are too many to rename casually by me, and we don’t support it. May I ask why you do case sensitive FS? I’ve been doing unix before NeXT/Apple days and never had the need for it.
I’ve been using unix systems like Solaris, AIX and Linux for decades, they are all case sensitive.
Mac being based on unix is providing an FS shortcut exposing case insensitive file systems. I prefer to use case insensitive file systems since as a programmer when I deploy my applications to their destinations they will always work.
Defaulting your programming paradigm to case sensitive on your development machines will result in less issues like this.
At least you should have better or proper error handling. I’m just analyzing this purchase as a hobbyist, but as a programmer I expect better from products I spend $700 on.
I too am running into the same crash upon launching SU 2017. Upon launching, I get the “Welcome to Sketchup” screen. Immediately upon clicking “Start using Sketchup”, the app crashes. BugsplatReporter shows up in the Macos launch bar and disappears in a second.
Can someone help please?
Here is what I see in console:
1/4/17 5:16:26.622 PM SketchUp[44483]: objc[44483]: Class SKTextPath is implemented in both /Applications/SketchUp 2017/SketchUp.app/Contents/MacOS/SketchUp and /Applications/SketchUp 2017/SketchUp.app/Contents/Frameworks/SketchUpAPI.framework/Versions/A/SketchUpAPI. One of the two will be used. Which one is undefined.
1/4/17 5:16:28.343 PM SketchUp[44483]: objc[44483]: Class HLRExporterBase is implemented in both /Applications/SketchUp 2017/SketchUp.app/Contents/PlugIns/Skp2AcadHlr.plugin/Contents/MacOS/Skp2AcadHlr and /Applications/SketchUp 2017/SketchUp.app/Contents/PlugIns/Skp2AcadSection.plugin/Contents/MacOS/Skp2AcadSection. One of the two will be used. Which one is undefined.
1/4/17 5:16:28.667 PM SketchUp[44483]: BugSplatFramework: exceptionHandler: shouldLogException name: NSUncaughtSystemExceptionException
reason: Uncaught system exception: signal 5
mask: 4
1/4/17 5:16:28.667 PM SketchUp[44483]: NSExceptionHandler has recorded the following exception:
NSUncaughtSystemExceptionException – Uncaught system exception: signal 5
Stack trace: 0x7fff86cc5c4f 0x7fff9830752a
1/4/17 5:16:28.667 PM SketchUp[44483]: BugSplatFramework: exceptionHandler: shouldHandleException name: NSUncaughtSystemExceptionException
reason: Uncaught system exception: signal 5
mask: 8
1/4/17 5:16:28.667 PM SketchUp[44483]: BugSplatFramework: getCrashReport: /Users/nitin/Library/Logs/DiagnosticReports/SketchUp
1/4/17 5:16:28.669 PM SketchUp[44483]: BugSplatFramework: sendCrashReport: BugsplatReporter is running
1/4/17 5:16:28.703 PM com.apple.xpc.launchd[1]: (com.sketchup.SketchUp.2017.342432[44483]) Service exited due to signal: Killed: 9
The first few warnings about duplicate classes have been typical of SU on Mac for a long time. They seem to reflect some sloppy organization of the SU code base, but they are harmless warnings. I’ve reported such to Trimble before.
The lines starting with the one saying “BugSplatFramework:” pertain to the crash, but don’t provide enough info to tell what was really going on. If you open the OS X console and look in the User Reports section you should be able to find a bugsplat log or a crash file from the time when SU tanked. The top part of that report will contain info about what SU was doing at the time of the crash - very technical so it won’t make sense to most users, but it’s what BugSplat would send to Trimble. If you copy that and paste it here (enclose between sets of triple back-ticks ` to keep the forum software from mangling it) someone from Trimble may be able to diagnose the cause.
Mac OS X is by default case-insensitive but case-preserving. The former means that “foo” and “Foo” are considered to be the same name, so can’t both exist in the same folder. The latter means that if you originally created a file named “Foo”, it subsequently won’t match a search for “foo” (and vice versa). And yes, that criss-cross can be confusing! Most Mac users go through the Finder and system open dialogs, so they never notice.
I find nothing in the “User Diagnostics Reports” section of Console. Seems like BugsplatReporter deletes it after sending to Trimble(?)
The only additional information in the logs is -
1/4/17 6:26:55.384 PM SketchUp[44658]: objc[44658]: Class SKTextPath is implemented in both /Applications/SketchUp 2017/SketchUp.app/Contents/MacOS/SketchUp and /Applications/SketchUp 2017/SketchUp.app/Contents/Frameworks/SketchUpAPI.framework/Versions/A/SketchUpAPI. One of the two will be used. Which one is undefined.
1/4/17 6:26:56.257 PM SketchUp[44658]: objc[44658]: Class HLRExporterBase is implemented in both /Applications/SketchUp 2017/SketchUp.app/Contents/PlugIns/Skp2AcadHlr.plugin/Contents/MacOS/Skp2AcadHlr and /Applications/SketchUp 2017/SketchUp.app/Contents/PlugIns/Skp2AcadSection.plugin/Contents/MacOS/Skp2AcadSection. One of the two will be used. Which one is undefined.
1/4/17 6:26:56.469 PM SketchUp[44658]: BugSplatFramework: exceptionHandler: shouldLogException name: NSUncaughtSystemExceptionException
reason: Uncaught system exception: signal 5
mask: 4
1/4/17 6:26:56.470 PM SketchUp[44658]: NSExceptionHandler has recorded the following exception:
NSUncaughtSystemExceptionException – Uncaught system exception: signal 5
Stack trace: 0x7fff86cc5c4f 0x7fff9830752a
1/4/17 6:26:56.470 PM SketchUp[44658]: BugSplatFramework: exceptionHandler: shouldHandleException name: NSUncaughtSystemExceptionException
reason: Uncaught system exception: signal 5
mask: 8
1/4/17 6:26:56.470 PM SketchUp[44658]: BugSplatFramework: getCrashReport: /Users/nitin/Library/Logs/DiagnosticReports/SketchUp
1/4/17 6:26:56.472 PM SketchUp[44658]: BugSplatFramework: sendCrashReport: BugsplatReporter is running
1/4/17 6:26:56.495 PM com.apple.xpc.launchd[1]: (com.sketchup.SketchUp.2017.342432[44658]) Service exited due to signal: Killed: 9
I tried a workaround by using Disk Utility to create a 1GB image file that had the default case insensitive file system on it. I then mounted this image and installed SketchUp to it. However, that did not fix the crash.
Without being there looking over your shoulder I can’t even guess why your experiment failed (and maybe not even then!).
I’m not a Trimble employee, so I can only collate what others have reported:
The crash on launch on Mac has only been reported by a small number of people so far who can’t isolate it to an errant extension, incompatible graphics hardware, or incorrect installation.
The only common feature identified is that all of those people have a case-sensitive filesystem on their Macs. @Barry has confirmed that SU will crash on launch on such filesystems.
There is a technical explanation for why trying to launch the app on a case-sensitive filesystem would fail: the library loader can’t find some vital files because their names as compiled in the application don’t match the capitalization of the files as saved on the disk. Nothing useful will be achieved by speculating about how that came to be, but it is the situation.
In another topic, @Barry has summarized Trimble’s current position about this problem (Barry, don’t let me put words in your mouth, please correct this if I have misread): a) it affects only a small number of Mac users, so it isn’t getting priority compared to bigger issues they face right now, and b) it is going to be overcome by events when Apple rolls out APFS sometime soon.
Personally I don’t find b) very satisfactory, since not everyone will immediately update to APFS, but a) is a business decision.
I don’t think it’ll work until you also do file system links to /Applications/SketchUp 2017 and ~/Library/Application Support/SketchUp 2017/ . I will try this later today.
I did create an APFS (case-sensitive new Apple filesystem that’s on Sierra as a beta), and it does crash as well.
A note of warning on 2016 - it MAY work, it may not… we don’t support case-sensitive filesystems on ANY version of SketchUp. You could try disabling the Ruby API, which may be a partial cause for some people’s systems.
OK, I was able to get SketchUp to run on case-sensitive by disabling the Ruby API.
Open terminal, and paste this:
/Applications/SketchUp\ 2017/SketchUp.app/Contents/MacOS/SketchUp -DisableRubyAPI YES
SketchUp should open and run, but anything using the Ruby API wont. I tested basic tools, and they worked. Hope that’s a usable workaround for at least some of you.
Just a bump to indicate that I have the same problem. I downgraded to 2016.
I use a case-sensitive file system as well as I move between Mac OS and *nix constantly. If there is anyone here who has influence over the source, I really wish programmers wouldn’t make this mistake. You basically have to go out of your way to type in a filesystem path “foo/bar” instead of copy/pasting the actual “Foo/Bar” from the command line. It really isn’t hard to handle case-sensitivity…
As I noted above, it’s the Ruby API that caused it on one of my machines. The Extensions team is aware of the issue.[quote=“tegtmeye, post:34, topic:35098”]
It really isn’t hard to handle case-sensitivity…
[/quote]
No, but it’s hard to prioritize fixing it right now when (a) I count the complaints on one hand, and (b) it will have to be fixed or APFS disks in the near future.
OK, you need another finger now. I also use a case sensitive file system for Linux compatibility. I am a web site developer and all the company web servers run Linux, which is case sensitive so to be able to reliably transfer files back and forth I use a case senstive Mac file system too.
Sketchup 17.2.2554 always crashes with a Bugsplat on startup.
I note Barrys workaround of invoking with
open /Applications/SketchUp\ 2017/SketchUp.app --args DisableRubyAPI YES
gets past the crash. Thanks for that Barry.
I would have thought the smart thing for OSX developers to do is run case sensitive, then your program will need to get the file name case correct and work on any type of installation.
###Having the same issues as is everyone with a case sensitive file system. Which is obviously more people than you can count on your hand…
##Customer focus
You know the impact is larger than the replies in this post and prioritizing based on complaints filed in a forum is… a bad practice. If one person complained in a forum that sketchup didn’t launch on any system you wouldn’t say thats a low priority. Just my 2 cents as a software engineer.
I do understand prioritization and I’m sure a large portion of the community is unaffected but the rhetoric you put out to your customers matter.
I believe feedback is important and helps us grow so I figured I’d write this on top of just my +1.
Sigh…I know it’s your first post and all, but a couple of suggestions:
Don’t post in bold and red: I’m an engineer, I hear your argument based on it’s merits, not the fonts you use.
I do understand the numbers of the problem, because (a) doing calculations like this is one of the ways you get hired as a Google engineer back in the day, and (b) I have a pretty good grasp of most of the numbers involved (having worked for case-sensitive NeXT and case-preserving Apple after the acquisition). “If one person complained in a forum that sketchup didn’t launch on any system you wouldn’t say thats a low priority” tells me you’ve never worked on software that has millions or billions of users. SketchUp will not launch on the steam-powered Babbage engine. I will say that’s a low priority.
My previous boss from 2(b) had lots of wonderfully colorful phrases, and if you think my “rhetoric” is bad, all I can say is I learned it from the best. And it really held him back, didn’t it?
You ignored the fact that this was an immediate answer in the context of January 10, 2017. I did not say we’ll never fix that. In fact, I said the opposite: we have to fix this to work with Apple’s next major OS release. I think most of our forum users understand that I will do my best to get them answers and advocate for them, and they understand me. You do not. Give it some time.
