When loading a new Potree2 model, the OctreeLoader class does not re-use existing Workers. This means that everytime a new Pointcloud is added, both a new WorkerPool and new Workers are created for that specific PointCloud. This is a performance issue, and could cause the browser to crash if too many PointClouds are generated over the lifetime of the app.
You can easily reproduce this issue with the example in this repo. Load the example, and repeatedly 'Load' and 'Unload' the Potree2 model. You will see new Workers are generated every time the PointCloud is loaded. I was able to easily generate 50+ workers by toggling the PointCloud on and off:
When loading a new Potree2 model, the OctreeLoader class does not re-use existing Workers. This means that everytime a new Pointcloud is added, both a new WorkerPool and new Workers are created for that specific PointCloud. This is a performance issue, and could cause the browser to crash if too many PointClouds are generated over the lifetime of the app.
You can easily reproduce this issue with the example in this repo. Load the example, and repeatedly 'Load' and 'Unload' the Potree2 model. You will see new Workers are generated every time the PointCloud is loaded. I was able to easily generate 50+ workers by toggling the PointCloud on and off: