Is there any way to release the tfjs-tflite model's memory? - Like dispose in GraphModel.
Then I can set it to window.onbeforeunload function (called when the browser page is refreshed or closed).

I solved this issue by following implementation:

window.onbeforeunload = function()
{
	model.modelRunner.cleanUp();
	model.modelRunner = undefined;
}

Please, add it to documentation.
There are no information how to release memory at all, especialy after page refresh:
https://js.tensorflow.org/api_tflite/0.0.1-alpha.10/

Hi, @Jove125

I apologize for the delayed response and good to hear that you're able to resolve your issue and as far my current understanding tfjs-tflite doesn't have a direct dispose() method like GraphModel, here are effective ways to manage model memory and release it when needed:

1. Dispose of Tensors: Explicitly release memory used by tensors after you're done with them:

const inputTensor = tf.zeros([1, 10]);
const outputTensor = model.predict(inputTensor);

//perform operations with outputTensor

outputTensor.dispose(); // Release tensor memory

2. Wrap Code in tf.tidy() : it will automatically dispose of all tensors created within a block as mentioned in this example tf.tidy

NOTE: Variables do not get cleaned up when inside a tidy(). If you want to dispose variables, please use tf.disposeVariables() or call dispose() directly on variables.

3. Use window.onbeforeunload to release memory before page refresh/unload as you mentioned in your solution

Thank you for your valuable suggestion and solution, as you mentioned in your issue template it's happening on some devices so I'll discuss this issue in our internal meeting and will update you soon on adding this solution in our official documentation

If possible could you please help me with your Github repo or code snippet ( along with model file) with complete steps which you followed before encountering the error so I'll go ahead and replicate the same behavior from my end also ?

Thank you for your cooperation!

Hi, @gaikwadrahul8,

I had this error in the application that allocates memory not only for models, but also for textures, opencv.js and more. It is not so easy to reproduce the dump itself using only initialization of models (or the model should be "heavy"). But I specifically checked that the problem is after initializing the models (there was no error without loading the model, no matter how many times I refreshed the page). And it disappeared after implementing window.onbeforeunload function.

The memory used by the tab (and not just the application) should be monitored.
I assume that when multithreading is enabled, the memory allocated in separate threads is not released when the page is refreshed or another page is open on the same tab (or it is released, but not immediately).