You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Code generated by KS does a fairly good job at not reading the whole file in memory and even doing stuff lazily where possible, but HexViewer component of ksv currently works with a byte array buffer, which is always filled up like that:
So, effectively it means that huge files would be read fully into memory before doing any visualizations at all. Partially, it depends on kaitai-io/kaitai_struct#44, but even without that probably we could do a IO-based instead of preread byte array based HexViewer.
The text was updated successfully, but these errors were encountered:
Code generated by KS does a fairly good job at not reading the whole file in memory and even doing stuff lazily where possible, but HexViewer component of ksv currently works with a byte array buffer, which is always filled up like that:
So, effectively it means that huge files would be read fully into memory before doing any visualizations at all. Partially, it depends on kaitai-io/kaitai_struct#44, but even without that probably we could do a IO-based instead of preread byte array based HexViewer.
The text was updated successfully, but these errors were encountered: