The current implementation of flock.bufferLoader attempts to load all its buffers at the same time, delegating to the browser to appropriately parallelize the decoding process. In practice, Chrome will crash if large numbers of large buffers are specified to a bufferLoader.
To be safe, flock.bufferLoader should sacrifice a certain amount of efficiency by loading its buffers sequentially, ensuring that the browser won't crash or become overloaded. In the future, parallel loading could be done more conservatively.
The current implementation of
flock.bufferLoader
attempts to load all its buffers at the same time, delegating to the browser to appropriately parallelize the decoding process. In practice, Chrome will crash if large numbers of large buffers are specified to a bufferLoader.To be safe,
flock.bufferLoader
should sacrifice a certain amount of efficiency by loading its buffers sequentially, ensuring that the browser won't crash or become overloaded. In the future, parallel loading could be done more conservatively.