After starting for a very long time (a day or more) the web application that I wrote (JS / HTML5) starts to act "weird". First of all, it stops sending normal data that it should do to the backend, where I expect it to send ~ 500 kb of data, and start sending just a few bytes of stupid things. I suspected that this was due to memory (unable to allocate memory or something like that), and when I explored, I saw something really strange and seemingly impossible, which suggests that this is a Chrome error, which I encounter, perhaps due to high memory usage. But I could use some confirmation from someone who knows better than me.
The main oddity seems to be that console.memory is splashing out. A related document states that "usedJsHeapSize cannot be greater than totalJsHeapSize", which is very, very. This also exceeds the heap size limit, which I think should not be:
Then I tried to understand what devtools could tell me, and made a moment of memory at that moment, for a few seconds, and looked at what he was saying .... the memory ranges from some negative insanely large number to 0B. This does not seem right.
And I checked the chrome: // memory report and when it uses a lot of memory, comparing this to the other Chrome browsing sessions that I have, it does not look fancy.
Can anyone confirm that this is a Chrome bug and the expected behavior of the developer tool. I do not interpret correctly.
Thanks!
javascript google-chrome memory google-chrome-devtools
Quinxy von besiex
source share