Possible memory leak on the website when Pl3xmap is open for a long time

[Kelzky]

Paper: 1.21.10 - build 76
Browser: Google Chrome
Pl3xmap version: 1.21.10-537
Webserver: Internal

After the Pl3xmap has been open in Google Chrome for a while, it starts to use more and more memory until the computer begins to slow down to an unusable state because it has run out of memory.
Closing the tab and opening it again resets the memory usage. The highest amount of memory observed is 7.6GB, the attached images show 3GB usage after starting at 70.2MB.

Steps to reproduce:

1. Open Pl3xmap on Google Chrome
2. Leave the tab open for an extended period of time
3. Notice the issue

Expected result:
Memory usage for the map should remain close to the value when loaded for the first time

[DereC4]

oop nice find

[Ericlyclyclyc]

Take a look at your DevTools and you'll find why.

This is because the server is retrieving the layers' data(and settings) to your client to update the map, and your browser just cached them in your memory. It's seemsly not a leak problem but the cache controling issue.

A nice solution of this problem is to use websocket instead of fetch api because browsers don't cache websocket messages but they cache fetch api data.

To avoid issues of memory leaks in other frontend code, I believe a more thorough inspection of the frontend code is needed before drawing any conclusions.