airsdk
[AIR 51.1.3.10 - Windows] Error #3691: Resource limit for this resource type exceeded - only after screen change
Problem Description
[AIR 51.1.3.10 - Windows] - Also other 50 and 51 versions. An application that works perfectly, using Starling, latest version.
The application works perfectly when context3d is created on any screen on the system (runs on a 3090 with 24GB Vram, GPU memory is not an issue.) But, if a screen-change happens, the GPU limit is brought to 512 MB, and the app crashes as soon as a few textures are loaded. It also limits texture size to 4096x4096, while if the screen does not change, I can load larger textures.
This happens both if a screen change occurs before loading any texture or when textures are already loaded, and also if, before loading any textures, the app is brought up again on the original screen. Also with ignoreResourceLimits = true;
Steps to Reproduce
1 - Launch the application on the primary screen (The application creates the Starling app but does not load any texture yet.) 2 - Move the main ApplicationWindow to another screen using keyboard and resizeToScreen(); 3 - Move it back to the primary screen 4 - Start the performance and load textures - boom, the error 3691 happens as soon as 512MB is hit. (If the app is not moved around screens but left on the screen where it started, any screen, it runs smoothly, loading all the required textures.)
OR
1 - Start the app and start loading textures. 2 - Move it to any screen 3 - The app crashes with that error once 512MB worth of textures have been loaded.
Give us a minimal example:
The app is in fullscreen. Just create a starling app that loads over 512MB worth of textures and change the screen of the main window. Use resizeToScreen() and then set to StageDisplayState.FULL_SCREEN_INTERACTIVE. Screens are of different resolutions: the primary is 4K, the secondary is 2K, and the tertiary is 1080. They are all connected to the main 3090 GPU. The error occurs either if 512MB is hit or if a texture is loaded that exceeds 4096 on one side (again, it works well if the screen has not changed.)
UPDATE: It also happens if I move the main window across screens manually using windows hotkeys.
@2jfw - thank you, but it is not related to https://github.com/airsdk/Adobe-Runtime-Support/issues/2388 This only happens if I move the main window to another screen; otherwise, everything works well. I had already tried ignoreResourceLimits = true;
Somehow, moving the app to another screen, resets GPU settings to low specs. It also happens if I move it BEFORE creating any Context3D.
