Dynamic Lighting Causes Frequent Crashes

I recently changed over from legacy Fog of War to Dynamic Lighting in one of my campaigns, but in doing so, it causes memory usage spikes that crash Roll20 on my computer. My computer certainly isn't new, but even with dynamic lighting on, my RAM usage sits at around 23% or so until a random spike will instantly crash the application. These crashes happen as often as every 3 minutes, and as a result make the application unusable. I got so fed up that one of the players in this campaign took over DMing so we could see if he also had the same problem. He has a much newer computer with better specs in every way, but even he has crashes using dynamic lighting. Is there a quick fix for this, or are we just up the river unless we use legacy Fog of War? I really like dynamic lighting, but I can't use it if it's going to crash my application.

By "application" you mean your Browser I assume? What Browser do you use for Roll20? You might want to have a look at this thread here as well:&nbsp; <a href="https://app.roll20.net/forum/post/11216045/high-processor-usage-chrome" rel="nofollow">https://app.roll20.net/forum/post/11216045/high-processor-usage-chrome</a> Do you have any addons or extensions enabled that could meddle with Roll20 in any way? Did you use Polygon Lines or handdrawn Lines for DL? How big is the map and how many Lightsources are there on it?

Chrome for browser, I have adblock on but Im a pro user so no ads, and I'm playing Tamoachan, which has a pretty big map for the lower levels. They are polygon lines, but ofc I didn't do them. If map size can cause the issue, then that's probably it because the Lower Levels of Tamoachan is a huge map.

Jacket said: Chrome for browser, I have adblock on but Im a pro user so no ads, and I'm playing Tamoachan, which has a pretty big map for the lower levels. They are polygon lines, but ofc I didn't do them. If map size can cause the issue, then that's probably it because the Lower Levels of Tamoachan is a huge map. Then this might be the cause for you Problems... To be certain, please try one other thing: reduce the Map size OR test it on another - smaller map. If you have the same Problems on a smaller map, then the issue is something else...

Are you using Explorer Mode? If so try turning that off, it is a resource hog.&nbsp;

Yes, we were using Explorer mode. I will try Permanent instead and see if it's better. Thanks!

Thank you for this post, it helped with an issue i had.