This is a continuation of the issue identified in: Sketchup Pro 2026 gets "jerky" quicker than 2025 - memory use?
This issue is continuing. with the help of Claude I was able to identify temporary remedy. Going back to the classic graphics engine. Unfortunately, per the message sketchup gave me when changing back to the classic engine, I now cannot use the advanced new features such as ambient occlusion,etc. I’m now running much faster hardware than when this issue was originally identified.
The sketchup dev team needs to pay attention to this.
Here is my chat with Claude about this issue, (interestingly it referenced my original, now closed post above)
What information is there about sketchup performance? I have a house model, after using sketchup for a period of time, the application gets very sluggish. If I do a save it gets a little better, but continues to degrade. If I close the application, and restart, it is good again. Using taskmanager once the memory is above about 3gb,it starts to get bad. My machine is a recent gaming grade system, with 32gb memory, a 5070 gpu, ssd, 275hx core i9 ultra cpu. Sketchup is set to use the GPU. When the sluggishness happens, there is not high cpu or gpu usage.
Synthesized memory management root causes and diagnostic troubleshooting strategies
Good news: what you’re describing isn’t a hardware problem — it’s a well-documented SketchUp behavior, and your build is more than capable of running it well.
This is a known pattern, not your hardware
SketchUp’s own help documentation confirms this exact symptom: SketchUp can slowly use more memory the longer it’s open and you are actively modeling, and if you’ve been working for a few hours in a row, saving your work and closing SketchUp — or restarting your device — can help. That’s precisely the save-helps/restart-fixes-it pattern you’re seeing. SketchUp
It’s also not unique to you — a SketchUp Pro user reported the identical threshold effect just a few months ago: 2025 would start getting jerky when memory use (per Task Manager) got close to 8GB, while 2026 exhibits the same issue around 5GB, and saving and restarting makes the problem go away for a while. Your ~3GB threshold fits the same pattern, just on the lower end. SketchUp Community
Why CPU/GPU stay quiet while it’s happening
This is the key clue. SketchUp is not GPU-limited like games or renderers — it’s CPU-bound by a single-threaded geometry kernel that cannot leverage multiple cores, so an expensive GPU sits mostly idle while a simple model crawls across the screen. But single-core CPU bottlenecks usually do show up as one core pegged at 100%. Since you’re seeing neither CPU nor GPU spike, the stutter is most likely coming from something in between: internal memory bloat inside SketchUp’s own process (heap fragmentation, huge undo stacks, thumbnail/texture cache rebuilding) causing pauses that Task Manager doesn’t register as “usage” the way a compute-bound task would. Hone
Likely contributors in a house model specifically
- Undo history — every edit action stays in memory for the session; hours of modeling without clearing it adds up.
- Unpurged data — your model stores all the components, styles, and materials you’ve added even after you’ve erased or replaced them, and they hang around taking up resources unless purged. Run Window > Model Info > Statistics > Purge Unused — this does more than a plain save. sketchup
- Navigation itself adds memory — one user found simply orbiting, panning, or zooming could increase memory by 500MB+ within 10 seconds, separate from any actual edits. SketchUp Community
- Extensions — background Ruby extensions (renderers, dynamic components, warehouse plugins) can leak memory quietly even when idle; poorly optimized plugins can degrade performance even when not actively in use. Hone
- Textures/materials — a 4096×4096 texture uses 16 times more memory than a 1024×1024 one, and when VRAM fills, the system swaps to slower system RAM, causing viewport stuttering. House models pulled from 3D Warehouse often carry oversized textures without you realizing it. Hone
What to try
- Purge unused every save (not just save) — Window > Model Info > Statistics.
- Disable extensions one at a time to isolate whether one is leaking — disable extensions one by one in Extension Manager and test performance after each. Hone
- Keep the Ruby Console closed if you use it — leaving it open is a known drag on performance.
- Check texture sizes on any imported/warehouse components; downscale anything oversized.
- As a test, try switching to the Classic graphics engine (Preferences > Graphics) for a session to see if the degradation curve changes — this isolates whether the newer DirectX/Metal-based engine is part of it.
- Until root-caused, treat periodic save-and-restart as a legitimate workaround, not a failure — Trimble’s own guidance says to do this on long sessions.
If you’d like, I can connect to your live SketchUp session and pull actual model statistics (entity/component counts, unused data, texture sizes) to see what’s really driving the memory growth in your specific house model — just let me know if it’s open right now.
