Memory Overallocation from tfjs version 0.12.4
See original GitHub issueTensorFlow.js version
0.12.4 ~ 0.12.6
Browser version
Chrome 68.0.3440.106 , Firefox 61.0.2
Describe the problem or feature request
From tensorflow.js 0.12.4, when running a model with large input, RAM memory is abnormally allocated to the extent that it can’t handle the data.
Code to reproduce the bug / link to feature request
With tfjs posenet demo official repository, the bug can be reproduced.
To see working situation in 0.12.3
- clone the posenet demo repository, link
- version up the tfjs version to
0.12.3
by editing package.json (before editing the version is0.11.4
in master branch) - start the demo server:
npm i && npm run watch
- change the input setting, and we can see the memory is in normal situation.
To see memory bug situation in 0.12.4 ~ 0.12.6
- clone the posenet demo repository, link
- version up the tfjs version to
0.12.4
by editing package.json (before editing the version is0.11.4
in master branch) - start the demo server:
npm i && npm run watch
- With the same input setting, we can see the memory overallocation with the demo application failing to work
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:10 (6 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@MoonsuCha Thanks this gives us an idea of what could be the cause (paging). Could you add the following lines to camera.js at around line 24 (after the imports):
Could you paste the output you get from that here? It should be at the top of the console
If that paging threshold is too low for an activation it could cause the problem you are seeing (and provide some data for us to fix it).
A workaround you could try is adding the following line after those console logs (near the top of the file).
this should turn of paging and possibly solve the problem (if its what I think it is).
I encountered the same issue when running a model on mobile devices. It turns out it’s easy to reproduce on a PC if you use a small screen width, which triggers paging.