Browser Memory Issues

Hi Everyone, Let me start by mentioning I am a player in the games I am playing, and not a DM. We are currently running Dungeon of the Mad Mage, and we know that he maps are very large.   There is the DM & 5 players, but we will on a nightly basis run into multiple browser/page crashes and need to reload.  It happens in both Chrome and Edge, so both Chromium. For troubleshooting, let me state that I have tested this with Hardware acceleration turn on and off.  With it turned off, I don't experience the memory issue but my CPU pegs at 95% as I move around the map and movement can take 5 to 10 seconds per square.  When it is turned on, movement is fine, but memory usage is huge and does not get freed up immediately.  It seems like this is related to Dynamic Lighting for as I move around I can see, with every update which includes other tokens which emit light, that my memory usage continues to increase and is never freed. I screenshots where I recorded it Roll20 Campaign Screen, Module initially loaded, After moving around various numbers of squares:  Pre-module load: 132MB Module Loaded: 569MB Moved 10 squares: 2.2GB Moved 30 squares: 4.8 GB Moved 60 squares: 8.7 GB Technical: Nvidia 3080 with latest drivers: 528.49 - 02/08/2023 CPU: i9-10850K Memory: 32GB

Have you tested using Firefox (the other supported browser) to see if the issue you are seeing is chromium only? As far as the memory usage, does your DM have Explorer Mode turned on? That keeps any of the map you have visited visible in greyscale when it is out of your token's line of sight.  If that is on, it might be worth them turning that off to see if performance improves.

It is enabled, and Firefox seems to behave like we have Hardware acceleration turned off.  It does not have the memory issue, but the movement lag is really bad (Reported via another player).  I will try it, as I don't currently have it installed.

Back after some testing with Firefox.  Band new install using Firefox 110.0... Pre-module load: 138MB Module Loaded: 401MB Moved 10 squares: 1GB -> 389MB (within 30sec) Moved 30 squares: 2GB -> 390MB (within 30sec) Moved 60 squares: 3GB -> 407MB (within 30sec) And input & movement lag did not seem to bad for me.  So the memory issue seems more like and issue with Chromium, possibly on the WebGL implementation  side of things.