<< Back to Warzone Idle Forum   Search

Posts 1 - 10 of 10   
Performance problems with playing from browsers: 2025-04-10 16:12:57

Piktor
Level 57
Report
Currently i am preparing for my first SASC, after digging the last year. Since some weeks I realize a massive slowdown in the Browser version, no matter if I play with Firefox, Chromium or Opera under windows and linux!
On one hand the memory footprint is incredible, after I checked through five running maps, the browser instance rises up to 2.2G (best viewed in firefox with about:processes )
The problem can't be solved, by going back to the level overview page, the memory is still allocated. My understanding was, that going back should delete all the allocated memory from the active map, but that is not the case.
You need to reload idle from scratch, to get memory back to a normal size of 330MB-450MB.
Playing in browser in the bigger maps (Triskelion, China, Europe Huge) is almost impossible. The memory exhaustion goes hand by hand with a real slow down of the whole game. Clicking a territory for occupying needs 3-10 seconds for changing the color.
I tried now different browsers, used new empty profiles, no change.
Another observation is, that when reloading idle (to reset the memory footprint after severl minutes of usage) idle now loads all the time the first of my five level. Before some weeks, it remembered the last used level and opened that level again. This change and the memory exhaustion seems to be happening since the same point in time.
Are other players making similar observations, or do I have to dig deeper in my system.


The warzon app however changed to a much better behaviour: Here is now the behaviour much more game friendly: When clicking on idle, it opens the level map, from where you can select, which level to play instead just opening either a random level or the topmost level. This behaviour is perfect for collecting AP, while already having at least two parallel levels. No more wrong artifacts when a level is randomly opened.


Here a memory map from firefox (about:memory), when playing Hardened Triskelion, while four more levels are active
2,104.45 MB (100.0%) -- explicit
├──2,050.07 MB (97.42%) -- window-objects/top(https://www.warzone.com/Idle/Play, id=32)
│ ├──1,828.89 MB (86.91%) -- active/window(https://www.warzone.com/Idle/Play)
│ │ ├──1,819.77 MB (86.47%) -- js-realm(https://www.warzone.com/Idle/Play)
│ │ │ ├──1,816.41 MB (86.31%) -- classes
│ │ │ │ ├──1,743.78 MB (82.86%) -- class(Array)/objects
│ │ │ │ │ ├──1,737.96 MB (82.59%) -- malloc-heap
│ │ │ │ │ │ ├──1,737.84 MB (82.58%) ── elements/normal
│ │ │ │ │ │ └──────0.12 MB (00.01%) ── slots
│ │ │ │ │ └──────5.82 MB (00.28%) ── gc-heap
│ │ │ │ ├─────69.21 MB (03.29%) -- class(Object)/objects
│ │ │ │ │ ├──44.43 MB (02.11%) -- malloc-heap
│ │ │ │ │ │ ├──33.00 MB (01.57%) ── slots
│ │ │ │ │ │ └──11.43 MB (00.54%) ── elements/normal
│ │ │ │ │ └──24.77 MB (01.18%) ── gc-heap
│ │ │ │ └──────3.42 MB (00.16%) ++ (10 tiny)
│ │ │ └──────3.37 MB (00.16%) ++ (5 tiny)
│ │ └──────9.12 MB (00.43%) ++ (3 tiny)
│ └────221.18 MB (10.51%) -- js-zone(0x12f7ba00)
│ ├──214.38 MB (10.19%) ++ strings
│ └────6.80 MB (00.32%) ++ (15 tiny)
├─────32.05 MB (01.52%) -- js-non-window
│ ├──23.19 MB (01.10%) ++ runtime
│ └───8.86 MB (00.42%) ++ (3 tiny)
└─────22.33 MB (01.06%) ++ (22 tiny)
Performance problems with playing from browsers: 2025-04-10 16:47:11

Dan
Level 45
Report
use https://www.warzone.com/ReportBug (Help > Contact > Report Bug)
Performance problems with playing from browsers: 2025-04-10 17:40:08

Piktor
Level 57
Report
=>> Are other players making similar observations, or do I have to dig deeper in my system?
Before reporting a bug, i will check if other are seeing similar issues.
Performance problems with playing from browsers: 2025-04-10 17:54:38

LetsAlly
Level 27
Report
I am having issues as well.
I remember playing on firefox/linux a few years ago, and everything worked so quick and snappy.
Returned to this game now after a few years, now again on firefox/linux, but, everything takes soooo long to load. after I sign in, I open the chat and Multi-player dashboard, but even that pages take a good half a minute to load at least. same with opening a game. I don't know what changes did the dev make, but it would be nice if they could review the code and compare from a few years back.
My memory usage with dashboard, chat, this thread, and a map open is 1.96 gigs, and after closing the map, it is 1.57 gigs with the rest of three tabs open.

Edited 4/10/2025 17:56:32
Performance problems with playing from browsers: 2025-04-10 19:01:36

Rob
Level 40
Report
I don't have performance problems like that, but I have noticed a clear distinction in speed between my computers and the app on my android device. The app is a little faster.

One of my computers is one year old, the other I forgot, but more than 5. For warzone, I only use Chrome.

Edited 4/10/2025 19:06:35
Performance problems with playing from browsers: 2025-04-10 22:10:37

Dan
Level 45
Report
The load time isn't something Linux-specific to website. The game used to be optimised for web and for app, but now it's optimised for the app, ever since Flash was replaced. For website, the game bundles up everything as a single JavaScript file that contains the entire app in a way browsers can understand, and applies that to every UJS/Babylon page, rather than loading only what's relevant to the page, or changing links to warzone pages to show the page without causing reloading. In Flash, entire pages weren't reloaded, so overall performance was better

Edited 4/10/2025 22:13:50
Performance problems with playing from browsers: 2025-04-11 02:49:01

Fizzer 
Level 64

Warzone Creator
Report
Thank you for reporting this. Performance should improve in the next update.

I investigated the issue and discovered a memory leak, which has now been fixed. I also made some enhancements to how Idle handles data storage. Previously, Idle stored its local data in the browser’s local storage, which is limited to 5 megabytes. To stay within that limit, it had to compress data before saving it—an extra step that negatively impacted performance.

Starting with the next update, Idle will use IndexedDB instead of local storage. This change provides significantly more space and eliminates the need for compression, resulting in better performance overall.
Performance problems with playing from browsers: 2025-04-11 09:54:33

Piktor
Level 57
Report
Thanks Fizzer for pointing this out. Do you have an idea, when this update may be available?

One more question: Do you check for available local storage, or do you compress by default?
As I have one Firefox profile for WZ, there is no problem increasing dom.storage.default_site_quota to 50MB or more.

Edited 4/11/2025 14:17:46
Performance problems with playing from browsers: 2025-04-11 15:55:19

LetsAlly
Level 27
Report
FYI, I don't play idle, but I still face long loading times for new pages. Thanks for your support!
Performance problems with playing from browsers: 2025-04-12 11:17:09

LetsAlly
Level 27
Report
Update: Community dashboard and forum opens up quickly, but mulitplayer dashboard, chat and all games open very slowly
Posts 1 - 10 of 10