-
-
Notifications
You must be signed in to change notification settings - Fork 293
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
uPython crashes - Error: Out of Memory #352
Comments
flipper has 256kb of ram and its never enough. we have extra features and it uses a tiny bit more that tips it over the point where its more likely to not work than to work. still, same issue on all firmwares with maybe slightly different chances of success |
@Willy-JL Why have uPython installed with you can't start it? |
you can start it, but its unlikely. |
I see, sadly it never worked for me yet. Also using the Momentum asset pack to save RAM and tried to start uPython after reboot. |
the momentum asset pack is among the heaviest in terms of ram usage. thats probably your issue. you probably go from 10% chance of opening to 0.1% chance of opening by using a large asset pack like that |
@Willy-JL I thought the momentum one is the smallest asset pack. It literally only has one short animation. |
animations are unloaded from ram before opening apps, icons and fonts are not. momentum pack has the most icons of any pack. the upython app on momentum also fully unloads asset packs icons and fonts before opening, but the impact of things being loaded before is that memory can become fragmented so in some cases thats not enough anyway. |
@Willy-JL Thank you very much! Which asset pack would you recommend that saves most RAM? |
default one, or the blank screen from the website if you want to go overkill |
@Willy-JL Thank you! I will close the ticket then I guess. |
Describe the bug.
When I try to start uPython it will crash after a short loading period.
The error message:
I never managed to start uPython.
Device Information
Reproduction
Target
No response
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: