question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot enlarge memory arrays.

See original GitHub issue

I don’t succeed in uploading a 800MB DICOM file to paraview-glance because of memory issues. How can I upload these larger files, without upgrading my RAM or VRAM? Thank you!

Error on a development server on Windows 10, 16GB RAM, 8GB VRAM:

Cannot enlarge memory arrays. Either (1) compile with  -s TOTAL_MEMORY=X  with X higher than the current value 1694498816, (2) compile with  -s ALLOW_MEMORY_GROWTH=1  which allows increasing the size at runtime, or (3) if you want malloc to return NULL (0) instead of this abort, compile with  -s ABORTING_MALLOC=0

Error on Ubuntu 18.04, 32GB RAM, 11GB VRAM:

Exception thrown while writing the image itkDICOMImageSeriesReaderJSBindingWasm.js:9:28594
<empty string> itkDICOMImageSeriesReaderJSBindingWasm.js:9:28594
itk::MemoryAllocationError (0x956ed0) itkDICOMImageSeriesReaderJSBindingWasm.js:9:28594
Location: "unknown" itkDICOMImageSeriesReaderJSBindingWasm.js:9:28594
File: /ITK/Modules/Core/Common/include/itkImportImageContainer.hxx itkDICOMImageSeriesReaderJSBindingWasm.js:9:28594
uncaught exception: Object
Line: 192 itkDICOMImageSeriesReaderJSBindingWasm.js:9:28594
Description: Failed to allocate memory for image. itkDICOMImageSeriesReaderJSBindingWasm.js:9:28594
<empty string> 2 itkDICOMImageSeriesReaderJSBindingWasm.js:9:28594

Issue Analytics

  • State:open
  • Created 3 years ago
  • Comments:11 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
florystcommented, May 26, 2020

Oh, hm that might be the switch from workerfs to memfs for itk.js virtual filesystem. Will have to investigate further to see how we can handle large files.

1reaction
thewtexcommented, May 22, 2020

@floryst this could likely be resolved, along with faster loading, with your WIP that enables separate series sorting / loading. In this case the pixel data is loaded incrementally, in slabs, in parallel, reducing memory usage.

Read more comments on GitHub >

github_iconTop Results From Across the Web

"Cannot enlarge memory arrays" error when document is big.
Sometime this error happens when a large image is forced to fit the page. In that case, if you taking the image with...
Read more >
Cannot Enlarge Memory Arrays Browser error - Unity Forum
Hello, I created a WebGL app, and ran it in a browser, then i got the error Cannot enlarge memory arrays. Either (1)...
Read more >
WebGL Player freezes with 'Cannot enlarge memory arrays ...
WebGL Player freezes with 'Cannot enlarge memory arrays' error when the 'Standard' Shader is always included in builds.
Read more >
Cannot enlarge memory arrays when allocating 1Mbytes buffer
"Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 16777216, (2) compile with ALLOW_MEMORY_GROWTH ...
Read more >
How can I solve this problem? "Cannot enlarge memory arrays."
"Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 2146959360, (2) compile with ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found