can we please work on this? LO 2025 is crashing with any LO file which has an SU 2025 model inserted in it. LO 2024 works on these exact same files without an issue.
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LayOut.exe_33ec639893f9c4aa632fc6458ed79794c9f20bb_25b0a9c4_6bf61577-1586-4b79-b5d6-7953b4344164
Could you try a more recent version of LayOut? There have been three updates since the one you’re using, and the second of those updates did fix a crashing issue when a SketchUp model is updating.
The third of the updates only came out today. It has a performance improvement in LayOut, but no crashing fixes.
Do you have bugsplat crash #'s or comments you added?
I tried to work it off your timestamp ( 0x68363888 = Tue May 27 2025 16:11:20 MDT) but that didn’t work (with timezone shifts).
The faulting module is ucrtbase.dll. Googling that, I found things like the articles below. I wish you would have responded in this detail in March when I asked. Let me know if these help your issue.
(Hmm… forum software is preventing me from posting the direct link… put an https:// and a answers.microsoft.com in front of these:
thanks for that. but it’s not the problem i.e. it’s not a windows problem. the fault is defintiely in the LO 2025 program.
i can open the file in LO 2024 - 235mb (for example), no problems. try to open same file in LO 2025 - crash. and it’s not file size dependent, it’s whether or not an SU2025 model is inserted or an SU 2023-2024 model. the LO 2025 can open a file with SU 2024 or earlier, but cannot open a file with SU 2025. LO 2024 can open any of them.
Another idea: can you have the LayOut 2025 file open without a model, and then insert the SU 2025 model, so we’d have some chance of creating a bugsplat report to work off of?
i’ll share with you the 2 files - one which is crashing, one which is not. PM with an email address (or two) i can add to the Google Drive shared folder.
@glennmstanton Im not sure if this helps. Ive had crashes in LO with no bug splat and a message box saying it could be related to the Experimental Graphics Engine. Turning that off didnt help but it did seem to be related to vector or hybrid viewports. Making those raster stopped the crashing. When I have to have hybrid for the detail I wait until im ready for final output to turn it on. However it doesnt seem to happen if the Vector or Hybrid is on a layer that has visibility turned off. I assume with visibility turned off that viewport isnt rendering.
Both files worked on Mac with the current version of LayOut (2025.0.659) and on Win11 LayOut (2025.0.660) the both versions crash with no bugsplat.
Here’s the funny part: the Crashing version says “This file is version: 2024” when I launch it on Mac, and the Not Crashing version says “This file is version: 2023” ?
Thanks for the files, Glenn. I’ve filed a bug and we’ll figure out what’s going on. The skp’s in the one you named “Not Crashing” were about 1/2 the size of the ones in the “Crashing” file, and that may have been the difference between my weak PC crashing and your PC not crashing.
@glennmstanton we have a fix and a workaround. The issue was that one of our core libraries was expecting stdout and stderr to exist (standard out and standard error). To workaround, you have to launch LayOut from a Windows command prompt with some parameters. Here’s the steps:
In Windows, type Win-R then “cmd” and hit enter, or input “cmd” on the Windows search bar.
Then type or paste this into the cmd window to launch LayOut:
“\Program Files\SketchUp\SketchUp 2025\LayOut\LayOut.exe” > NUL 2>&1
LayOut will launch, and we’ve been able to open the crashing file without issues.
We have a fix in our development environment. Our release schedule will dictate when we can ship this publicly. Thanks for your files and your help in hunting this down.
Yes, we’ve had 2 people verify that internally with the issue, but I’d like you to see if it works for you. I used command.exe, and I also wsl.exe (params are same except stdout to null is >/dev/null).
that works! i ran the command prompt window as administrator (running it as me, even though i am administrator didn’t launch it) and it opened and the files i couldn’t open before, now open and behave as expected.
looking forward to the update! maybe this same issue is causing other crashing as well… would be nice to have a fix for a more broad range on this…
not sure what the timestamp in the message refers to, perhaps the app file timestamp?