When I try to save a PLY file from Supersplat, it only saves a 0KB file, and Chrome complains about a lack of memory. The original PLY file is about 900MB in size. The PLY file was originally generated in Postshot.
I have 64GB of RAM and 24GB of video memory. What might help?
Hi @Olli ,
I’m so sorry you’re struggling with this. Other users have struggled with this too
The issue is we allocate enough memory for the entire output file during save and this can be larger than the memory chrome will allow.
We will be updating the code as a high priority to be more memory efficient anbd stream out the data instead, hopefully within the next week or so.
Thanks
It’d be worth trying this in Firefox. From what I’m reading online, Firefox does not impose a strict limit, unlike 4GB limit in Chrome.
Firefox seems to freeze as well during the save process.
Hopefully you’ll manage to fix this! 
I am quite sure I was able to save larger ~1GB files earlier so I wonder what has changed.
Were you doing much editing on the scene? The edit history can consume memory, which we currently don’t prune. If you were making lots of selection changes perhaps that’s why? We’ll be addressing this memory consumption too.
I was actually wondering whether running SuperSplat as a PWA might result in it having access to more memory. I’ll test this when I get a chance.
I got ChatGPT to generate a simple html file test how much memory can be allocated up to 32GB. On MacOS, I got this:
Chrome: 16GB
Firefox: 32GB (likely could do more)
Safari: 32GB (likely could do more)
Could you guys try running this in your browsers and observe the dev console?
Just stick this to test.html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Memory Allocation Test</title>
<script>
async function allocateMemory() {
const chunkSize = 500 * 1024 * 1024; // 500 MB
const maxMemory = 32 * 1024 * 1024 * 1024; // 32 GB
const chunks = [];
let allocatedMemory = 0;
console.log('Starting memory allocation test...');
try {
while (allocatedMemory < maxMemory) {
let chunk = new Uint8Array(chunkSize);
chunks.push(chunk);
allocatedMemory += chunkSize;
console.log(`Allocated: ${(allocatedMemory / (1024 * 1024 * 1024)).toFixed(2)} GB`);
// Wait a bit to avoid browser freezing
await new Promise(resolve => setTimeout(resolve, 100));
}
} catch (e) {
console.error('Allocation failed:', e.message);
}
console.log('Memory allocation test completed.');
}
</script>
</head>
<body>
<h1>Memory Allocation Test</h1>
<button onclick="allocateMemory()">Start Test</button>
<p>Check the console for results.</p>
</body>
</html>
After some investigation it seems I introduced a MEMORY HUNGY bug in the previous release. Busy fixing ASAP!!!