[Bug] Change Tool State Performance

[luojiong]

Describe the Bug

I loaded 360 DCM files and then performed threshold segmentation to select data. When I switched tools, I got stuck for about 5 seconds. I carefully analyzed the performance and he created and destroyed thousands of temporary objects

Steps to Reproduce

1. Perform threshold segmentation and select approximately 300 layers of threshold data

2. Switch the tool to a brush for brushing

3 When I was switching, I got stuck for about 5 seconds. I carefully analyzed the performance and he created and destroyed thousands of temporary objects

The current behavior

When I was switching tool , I got stuck for about 5 seconds

The expected behavior

I expect to switch tools very smoothly and in real-time

System Information

System:
OS: Windows 11 10.0.26200
CPU: (24) x64 Intel(R) Core(TM) i7-14650HX
Memory: 16.17 GB / 63.71 GB
Binaries:
Node: 24.11.1 - C:\nvm4w\nodejs\node.EXE
Yarn: 1.22.22 - C:\nvm4w\nodejs\yarn.CMD
npm: 11.6.2 - C:\nvm4w\nodejs\npm.CMD
pnpm: 10.26.2 - C:\nvm4w\nodejs\pnpm.CMD
Browsers:
Chrome: 144.0.7559.133
Edge: Chromium (142.0.3595.94)
Internet Explorer: 11.0.26100.7309

"@cornerstonejs/codec-charls": "^1.2.3",
"@cornerstonejs/codec-libjpeg-turbo-8bit": "^1.2.2",
"@cornerstonejs/codec-openjpeg": "^1.3.0",
"@cornerstonejs/codec-openjph": "^2.4.7",
"@cornerstonejs/core": "^4.13.1",
"@cornerstonejs/dicom-image-loader": "^4.13.1",
"@cornerstonejs/nifti-volume-loader": "^4.13.1",
"@cornerstonejs/polymorphic-segmentation": "^4.15.1",
"@cornerstonejs/tools": "^4.13.1",

[linear]

CS-121