SketchUp 2018 Quits When Exporting 2D Graphic


#1

Working on MacOS High Sierra version 10.13.4 with SketchUp Pro 2018. I just installed it new yesterday and when I try to export a project to a 2D graphic it quits right after I click 2D Graphic on the menu. No error messages nor BugSplat. Apple crash report does show up. I can instantly reopen it afterwards, with no issues and was able to export a 3D Model. I’m trying to export a file set to Hidden Lines with 2 Profile.


#2

Copy / Paste the Apple crash report to me in a Private Message and we’ll take a look. What graphics card, and graphics switching (if it’s a laptop) on? If so, hook up to power.


#3

It’s not letting me send you a Private Message. First it said that the message was too lengthy (due to the crash report), then it said I’m not allowed to message you.

NVIDIA GeForce GT 755M 1024 MB, Desktop
I forgot to mention I try to export it as a .pdf, so it crashes as it’s trying to export.


#4

Continuing the discussion from SketchUp 2018 Quits When Exporting 2D Graphic:
Apple crash report:
Process: SketchUp [47449]
Path: /Applications/SketchUp 2018/SketchUp.app/Contents/MacOS/SketchUp
Identifier: com.sketchup.SketchUp.2018
Version: 18.0 (18.0.16976)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: SketchUp [47449]
User ID: 501

Date/Time: 2018-05-23 12:01:05.170 -0500
OS Version: Mac OS X 10.13.4 (17E202)
Report Version: 12
Anonymous UUID: 8F1F54BD-1703-41CB-86F4-2D097A06AE17

Sleep/Wake UUID: 8C769A08-5E7B-4416-BEAC-265C8FD37DD2

Time Awake Since Boot: 430000 seconds
Time Since Wake: 10000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Application Specific Signatures:
Graphics kernel error: 0xfffffffb


#5

Turns out I was being blocked for being a new user. How stupid is that!


#6

Well, sorta, but the Discourse (forum software) guys are VERY sharp, Jeff Atwood also founded Stack Overflow and Stack Exchange and kinda has demigod status among sw engineers https://blog.discourse.org/2013/02/the-discourse-team/

Clearly, it’s a video card thing. I’ll pass along, and we’ll chat and pull in NVIDIA if necessary.


#7

Do I need to update my video card or do you think someone can figure out a work-around?


#8

Also, how’d you figure that out? Should be good knowledge for a rainy day. :slight_smile:


#9

The top 4-5 lines of a crash stack on thread one will give you the best clue. Anything with GL in it is OpenGL… we look for “ruby”, which is probably the leading crash cause: but hey, with great power comes great responsibility, and some people load ruby code from who-knows-where.

No response yet, but one of our graphics testers is out sick today.