Closed Adolio closed 3 years ago
Oh wow — no, I haven't heard of this issue before!
Yes, please try to find out if the GPU memory consumption (as shown by the stats display) rises over time.
Furthermore, it would be interesting if this happens only on Windows. There have been a few issues with DirectX since Adobe switched to DirectX 11 – this could be one more of those.
This issue happened again on my side on another machine after approximately one hour of play (still on AIR 32
with Starling 2.6.1
on Windows 10
under DirectX11 (Enhanced)
). This time it wasn't a standalone build, but it ran through adl.exe (32-bit)
.
GPU & standard memory looks good. No warnings & no errors from both Starling & AIR... 🤔
From my logs:
[2020-06-02 18:02:59.461] [INFO ] [Main] Current system memory: 128.84 MB
[2020-06-02 18:02:59.461] [INFO ] [Main] Current GPU memory: 592.20 MB
That's a really weird... again only the filters/shaders are broken (Display Objects getting invisible).
Note that there is high chance that this issue is related to: https://github.com/Gamua/Adobe-Runtime-Support/issues/38.
This issue is now fixed in AIR 33.1.1.217
🥳
Thanks Harman AIR Team!
Hi Daniel,
I recently noticed that all Display Objects with filters are not rendered anymore after several hours of the app running. When this occurred, there were no (uncaught) error thrown. The build was done using AIR 32 on Windows.
Do you know if someone has experienced the same issue in the past?
I would say that it sounds like a GPU out of memory issue... but unfortunately I don't know what was the memory state when it occurred. I have now added debug logs in few places to track that if I can reproduce.