-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
loaders.gl/las OOM Error #1912
Comments
If you are using the default setup, you are probably using the worker loader. You can set a flag to destroy the worker loader after each load: https://loaders.gl/docs/developer-guide/using-worker-loaders#disabling-reuse-of-workers. Perhaps using a fresh loader for each load will help? |
Thank you for the answer. I don't use the |
No you would need to use |
The
Of course, the warnings disappear if |
Haven't seen these. The LASLoader appears to work on the loaders.gl website: https://loaders.gl/examples/pointcloud (and I can see the las worker has started in the Thread inspector). Are these just warnings? Do the point clouds actually load? Not sure how to help... |
Yes, the point cloud files are loaded with As I load thousands of files, I get thousands of |
@gchoqueux Sorry for slow reply. In contrast to most loaders.gl loaders, the LAS loader is just a wrapper around a pre-compiled asm.js file (presumably the original source code is in C++). See https://github.com/verma/plasio. I will close this issue as unfortunately, I do not have a lot of knowledge about asm.js and browser differences related to that. I can say that long-term it would be very desirable to move to a pure Javascript (Typescript) LAS loader implementation. That would make this important loader much easier to maintain. |
ok, thanks |
ignore me, |
We use
loaders.gl/las
to load a large cloud with a multitude of laz files (entwine cloud).Then we visualize them simultaneously from hundreds of laz files with a library
THREE.js
.After uploading hundreds of files, the
loaders.gl/las
throwns OOM Error.It seems that this error is thrown when
emscripten
can't resize memory heap.Is there a memory leak?
Is there a memory limit?
is possible to free the
loaders.gl/las
memory?We have a open issue iTowns/itowns#1721
The text was updated successfully, but these errors were encountered: