There seems to be a problem with Content Cache and Query Model Objects, because I Grasshopper keeps triggering pushes again without changing the input geometry. This used to be working without retriggering pushes, which slows down the canvas considerably with further downstream processing.
Layer keeps pushing.3dm (225.9 KB)
Layer keeps pushing.gh (10.4 KB)
s
@kike I did some further trouble shooting and can rule out it has anything to do with the geometry or layer that I reference from (manually inspected each and every piece of geometry by deleting them individually). Replacing the Query Model Objects or Content Cache also did not affect this.
I don’t think there’s anything else I can do to diagnose this further.
Rhino 9 SR0 2026-3-25 (Rhino WIP, 9.0.26084.12305, Git hash:master @ 90319a3baf21c85605c6c0166e6376839504696d)
License type: Educational Lab License, build 2026-03-25
License details: LAN Zoo Network Node
Expires on: 2026-05-09
Windows 11 (10.0.26200 SR0.0) or greater (Physical RAM: 31GB)
.NET 9.0.1
Computer platform: LAPTOP - Plugged in [79% battery remaining]
Non-hybrid graphics configuration using DirectX
Primary display: NVIDIA GeForce RTX 4070 Laptop GPU (NVidia) Memory: 8GB, Driver date: 12-30-2025 (M-D-Y). DirectX(11)
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Secondary graphics devices.
AMD Radeon™ 610M (AMD) Memory: 1GB, Driver date: 3-3-2026 (M-D-Y).
> Integrated accelerated graphics device with 5 adapter port(s)
- Laptop’s primary display device
DirectX Settings
Safe mode: Off
OpenBLAS: OpenBLAS 0.3.30 DYNAMIC_ARCH NO_AFFINITY Cooperlake MAX_THREADS=64.
Rhino plugins that do not ship with Rhino
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 9 WIP\Plug-ins\Commands.rhp “Commands” 9.0.26084.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 9 WIP\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 9 WIP\Plug-ins\UpdatesAndStatistics\UpdatesAndStatistics.rhp “UpdatesAndStatistics” 9.0.26084.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 9.0.26084.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 9.0.26084.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 9 WIP\Plug-ins\MeshCommands.rhp “MeshCommands” 9.0.26084.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 9.0.26084.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles” 9.0.26084.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 9.0.26084.12305
C:\Program Files\Rhino 9 WIP\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 9 WIP\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 9 WIP\Plug-ins\SectionTools.rhp “SectionTools”
C:\Program Files\Rhino 9 WIP\Plug-ins\RhinoLabsTools.rhp “Rhino Labs Tools”
I can also rule out it’s a plugin conflict.
Hi @Intuos,
This will be fixed on the WIP released today.
Thanks, that’s great!
Okay, so there appears to still be an issue with Content Cache in that the automatic pushing does not delete the old geometry in a very particular case that I cannot reproduce in a simpler setup. If I manually hit the push button, everything works as expected.
Andy once asked me why I had Content Cache set to purge, it’s to avoid the automatic pushing on double data, because that triggers a loop in my case.
I will send the files in later via mail if anyone wants to inspect them.
E: Files are sent. Also want to mention that this script used to work correctly about three months ago.
I did not notice this earlier, but the entire setup is botched. The old geometry isn’t removed on push. And it is not in the input to push, so it shouldn’t even be there…
Thanks, we’ll take a look.
@Japhy do you have any idea what’s going on in the files I sent in? Or any other information so I can plan ahead?
Will I have to plan for extensive workarounds that may also not work as expected?
Should I try to reduce the plugin components for further trouble shooting?
@Japhy I sent in files that should contain no plugins, issue is still present.
@Japhy hunting through the script 3 times over I noticed that it started working again in a trimmed down version. Since it has been working before at times, I kept deleting parts and may have found a stray debugging Content Cache that may have been the problem (duplicate inputs were another issue after the recent Content Cache bug much earlier on), so I may have solved it. Will test thoroughly tomorrow. 
