+1 I crash on radial arrays too. Crashed 3 times in a row on the same operation a few days ago then magically worked. I always send the crash reports in. The struggle is real
3 Likes
hello, Iâm noticing some slowness with the new version (including the latest patch) compared to 2024. Am I the only one?
Thanks
Hi @Colin - I sent in a BugSplat with my email and description today, Sunday 23 Mar - doing a radial array on a compound roof building (part of a silo). I get this crash more often than not⌠of course I re-open SKP to make a screen capture and it worked fine. I always save before I do a radial array now.
1 Like
Looking at the log for one of your crash, I see these final steps:
Tool(RotateTool)
Tool(RotateTool)
Start(Rotate)Abort
Start(Rotate)Commit(636)
Tool(RotateTool)
Tool(RotateTool)
Undo(Rotate)
Start(Array)Commit(637)
That makes it look like you started a rotate, pressed escape, did a new rotate, undid that, and then made an array.
I tried replicate some of that, and did get a crash!
Unfortunately, my SketchUp session had been about two days long, and the log didnât have the last things I did recorded in it. But I will try more tests, and see if I can tell what is the significant action that leads to the crash.
1 Like
Not sure if this might be related. In SU version 25.0.571, with the DC extension installed (either enabled or disabled), pressing G then Q (or G then F) throws an error:
#<NoMethodError: undefined method `lengthâ for nil:NilClass>
c:/users/myUser/appdata/roaming/sketchup/sketchup 2025/sketchup/plugins/su_dynamiccomponents/ruby/dcobservers.rbe:590:in `onToolStateChangedâ
This is weird because you wouldnât think the DC tool observer would be doing anything (especially when disabled). The observed behavior is that the axis appears when G is pressed (expected) and then the protractor momentarily appears when Q is pressed before the error is thrown. SU returns to select mode. Maybe length is being passed when the rotate tool is expecting an angle? Maybe part of the puzzle of the Q problem?
I donât remember the exact order - but I often have to esc out because Iâm getting that floppy inference issue I posted about on the beta site. So likely I did start, stop, undid, etc.
I will pay more attention whenever I do this now.
I donât remember if I had the dynamic components option panel open but I did use it today to work with my window components and I have seen that error before.
Yeah - just putting it out there as possible part of the solution. I tried some radial arrays and couldnât get a crash.
Just uninstalled DC extension. Started a fresh instance of SU and still got the error. Itâs like some other extension or code in SU is looking for it. Hmm.
I do have shortcuts using G (shift + G and ctrl + G). Is this a shortcut thing (rhetorical)?
I think the Devs will have to look under the hood on this one.
1 Like
I havenât been able to use sketchup 2025 on PC for some days now, itâs working fine on Mac but on windows I had a crash some days ago, I sent the bug splat and it told me to update the drivers, I checked and new studio drivers were released a week ago, I thought it had fixed the crashing problem but it didnât, I went back to the driver I was using but it still doesnât work, it crashes without a bug splat report. Some times it opens after several attempts trying different ways to open it, but I donât have the time to do it all the time so Iâm still using 2024 on pc and 2025 on Mac.
Good to see the double click issue is under investigation. I do wonder if the input buffer is broken. Iâm not a qualified coder, but it seems I can click too fast for SU/LO at which point it hangs while waiting for other process to respond. Rarely I have recovered a âhungâ LO drawing by shutting down SU. Other times SU just flips to beachball mode and requires a âForce Quitâ. This in itself can result in unpredictable Bug Splat Report windows and missing autosave files.
James, I think you found two new bugs for the price of one. Let me explain. The Dynamic Component extension is waiting and watching for the user to attempt to change the axes of the entities inside of a dynamic component. If the user does this SU will display a warning to the effect that changes to the axes might cause the dynamic component to react strangely to any pokes from the DC pointy finger tool.
There are two bugs that pop up when the Dynamic Component extension is enabled.
The first, if you try to Make Component without any entities selected SU will pop up the axes tool. But note, if we donât have any entities selected the Make Component or Make Group commands should not be available.
The second is an error when setting the axes while making a component. Here are the step to cause the issue: draw two rectangles, select them, Make Component, Set Component Axes, click-click-click, push the Create button. An exception will pop up on the Ruby Console.
1 Like
I hadnât realized the bargain I stumbled upon! First, I updated to the latest SU '25. DC was installed (I had uninstalled it⌠but still got the error).
I see what you mean. dcobservers.rbe:590:in `onToolStateChanged' Works with one rectangle too (double click, too).
I looked at the javascript briefly for hints. Conclusion: I dunno.
Too bad DC isnât open source. If itâs 13 years old and little is happening with it (afaik), then why not just put it out into the wild? Presumably future versions of SU will have Live Components shipped. Or maybe not. But will DC always come with SU? Anyway, it seems people would tear into it, fix things and make new DC âstuffâ.
Has anyone here already adressed the window asking for purging components and materials when saving? There is a box which says: donât ask me again. If you choose not to ask again it will still keep asking you, which is kind of annoying.
Iâm not seeing that since I told SketchUp not to ask to purge. It implies to me that SketchUp was not installed correctly so the file that stores your preference is not getting written.
Close SketchUp and find the downloaded installer. Right click on it and choose Run as administrator. Then choose the Repair option. After it completes do a cold reboot of your computer. When it is restarted open SketchUp and go into Preferences>General. Untick the box for Ask to Purge All at save.
Save a SketchUp model file, quit SketchUp and reopen it. Check to see if the box is unticked.
the update checking servers appear to be down BTW certainly for a few of us here in the UK
in France too, I downloaded directlyâŚ
1 Like
I had it happen once yesterday and once today. but as I rebooted sketchup, I managed to copy without crashing so⌠I didnât send the splat.
Yup, thatâs why I deleted my post 
We have found the change that is likely to have introduced the new problem. The developer who did that change is looking into the new issue. That means there is some hope of finding out how to fix it.
3 Likes
Thatâs good news as in Layout copy/pasting from one document to another crashes every timeâŚ