Hi everyone,
I'm experiencing a performance issue that only occurs in Chrome fullscreen mode on Windows, and I'd love some guidance from the community.
Setup:
- ArcGIS JS API, 3D SceneView
- GraphicsLayer with ~400–500 graphics
- Graphics are stored in a JavaScript Map() keyed by ID for fast lookup and updates
- Continuous real-time updates to a subset of graphics (~30–50 at a time) covering position, symbol, and attributes
- The view qualityProfile is not set. (it's automatically choosen by the esri)
- Updates fire at millisecond intervals
The Problem:
Everything runs smoothly in a normal Chrome browser window. However, as soon as Chrome goes fullscreen (F11 or maximized to full screen), performance degrades significantly — the scene becomes sluggish and unresponsive.
The update logic itself is straightforward: we look up a graphic by its ID from the Map(), mutate its symbol, geometry, and/or attributes directly, and let ArcGIS reflect the change. No graphics are being removed and re-added on each update.
What I've tried so far:
- Verified the issue is consistent across multiple Windows machines with Chrome in fullscreen
- Confirmed the same code runs fine in a normal (non-fullscreen) Chrome window
- The issue appears tied specifically to the fullscreen state, not the number of updates
Questions:
- Is this a known issue with SceneView and WebGL canvas resolution scaling in fullscreen?
- Are there recommended patterns for batching or throttling real-time graphic mutations in a 3D SceneView?
Any insights or suggestions would be greatly appreciated. Thank you!
