Related to my previous post ( Can’t create arrays larger than 0x7fffffff bytes - Templates/Scripts - 010 Editor Forum (sweetscape.com)), it looks like 010 will stop responding if I select a template variable that is a huge array. Given that even selecting a 0x1000000 byte array has a noticeable delay in the UI, I imagine that it’s stuck dealing with all that data. I don’t know if that’s from highlighting it, reading it in, or something else, but it’s bad enough that Windows thinks the app is unresponsive.
We did find a bug that caused a slow-down selecting a huge array in 010 Editor. Could you check if this update performs better:
http://download.sweetscape.com/010EditorWin64Installer15.0.1b.exe
Again this is just for selecting an array. If you are trying to open a huge array in the Template Results that currently takes a huge amount of memory and will most likely bog down your machine. We are going to be trying some optimizations in the future to use less memory for opening large arrays.
Graeme
SweetScape Software
FYI: This is related to me working on improving the MKV file template. When I open a large video (~56GB in this case), the new version of the script executes pretty fast. When I expand one of the template elements (the big one with all the stream data in it), 010 crashes. I don’t know if there’s any way to collect a crash dump or something for you. I suspect what’s happening is that the file likely has an insane number of elements at the level being expanded and it runs out of memory. I could send the updated template but not the video. This is with the old version.
Anyway, related to the original issue:
The new version seems to handle selecting the large array fine. Performance is great, no issues.
I can’t easily repro the above crashing issue with the new version because I installed the new version in Windows Sandbox and I don’t know if I have space for a 56GB file and it can’t reach the network (where the file is currently stored). I’m in the middle of things, so rebooting to install the new version isn’t practical. I can do it later if you need me to.
If you are opening a large node in the Template Results tree and it crashes, the chances are very good that it is running out of memory. Depending upon how your template is written, it may be possible to restructure it so that not too many nodes are under one child, but it may be difficult to reorganize. We are planning on doing more work to make this work better in future versions.
Graeme
SweetScape Software