-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emulator fails with out of memory error #3270
Comments
That generally means that the app is unable to recover from a low memory situation i.e. where we've asked for a new region of memory (via the Windows "VirtualAlloc" call) but it's failed to return us anything, and the memory request had been considered to be crucial. So the runtime just aborts.. FYI we have a few changes going in to 51.0.1.2 because of this sort of thing though:
But it's worth keeping an eye on your allocations and making sure you e.g. dispose of any bitmap data or byte arrays properly... thanks |
Hi @ajwfrost , thank you for an answer, is it known when 51.0.1.2 planed to be published? |
Should be available first thing tomorrow.. |
@ajwfrost |
Both the changes I mentioned will be out in 51.0.1.2, so that should definitely help with your application... |
Hi,
When I run mobile application in emulator, it fails with message: "error: out of memory".
Problem Description
Describe your problem in detail. Include the following information:
Which AIR SDK did you use?
AIR SDK:33.1.1.300, 50.2.5.1, 51.0.1.1
Environment:
Microsoft Windows 11 Pro, Version: 10.0.22631 Build 22631, System type: 64 bit
Laptop: Lenovo IdeaPad Gaming 3 i7-12650H
Processor: Intel Core i7-12650H 2300 MHZ, 10 Cores, 16 Logical processors
RAM: 64GB
Video card: NVidia GeForce RTX 3050 Laptop GPU
Can you reproduce it yourself, or did you get reports from other users? If so, how many users are affected (percentage)?
Myself.
Steps to Reproduce
I run my application by next command line:
adl.exe -profile extendedMobileDevice -screensize 534x950:534x950 -XscreenDPI 326 -XversionPlatform AND C:\projects\slotagram_starling\webapp\flex\slotagram-mobile-boot2\target\slotagram-mobile-boot-app-android-localdev.xml C:\projects\slotagram_starling\webapp\flex\slotagram-mobile-boot2\target
After it application starts and begin to receive bitmaps from server and create a textures for them and during it the application crashes with message: "error: out of memory".
Give us a minimal example:
Looks like following peace of code is a last one before fail:
Below is attached archive with three logs of my application and three windows application crashing events from windows eventviewer, each pair per different versions of Adobe Air SDK: 33.1.1.300, 50.2.5.1, 51.0.1.1, and archive with my application descriptor
logs.zip
application-descriptor.zip
The text was updated successfully, but these errors were encountered: