Skip to content
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

repetaed bus fault & out of ram crashes #234

Closed
GameLord2011 opened this issue Sep 23, 2024 · 14 comments
Closed

repetaed bus fault & out of ram crashes #234

GameLord2011 opened this issue Sep 23, 2024 · 14 comments
Labels
duplicate This issue or pull request already exists

Comments

@GameLord2011
Copy link
Contributor

Describe the bug.

I randomly get "Bus Fault" and "Out of Ram" crashes.
How do I fix this?

Reproduction

I can't rember.

Target

Hardware? (idk)

Logs

No response

Anything else?

No response

@Willy-JL
Copy link
Member

Flipper hardware is very limited and we are pushing it to its limits. Simply, it's running out of ram. What you can try is changing what asset pack your using, since asset packs containing icons and fonts will consume some ram in background. Also some third party apps are coded a bit poorly and will leak memory, so after a while of using a flipper, a out of memory crash is normal. If you can reproduce a crash consistently, and disabled asset packs, then you might have a bug on your hands by we can try to fix.

@Willy-JL Willy-JL added the needs-more-info Requires more information to triage label Sep 23, 2024
@GameLord2011
Copy link
Contributor Author

k
it usually happens when using the nfc app

@AztecCodes
Copy link

AztecCodes commented Sep 24, 2024

Yes the issue with the NFC App is known. It was already reported.

Check the issue here in the Unleashed Repo: DarkFlippers/unleashed-firmware#778
The issue was also reported in Momentum Repo here: #144

Using the Flipper Zero and then starting the NFC App can lead to Bus Fault or Out of RAM Errors.

@Helios343
Copy link

Helios343 commented Sep 24, 2024 via email

@FalsePhilosopher
Copy link

FalsePhilosopher commented Sep 24, 2024

Hold your back arrow for the quick power off function, does it display the crying dolphin or just turn off power? Yesterday I upgraded from 75e to 78e and the issue persisted. I noticed the different power off menu and went about fixing it. Rebooted into DFU mode, repaired to 1.0.1 from qflipper, once it booted after install I formatted the sd card. I then installed 78e from qflipper and I got my crying dolphin back an it doesn't crash launching files from explorer. I have not done extensive testing, just launched a file from browser and micro python which crashed with a bus error the first time but launched the second time. I came to the UL issue to report my findings and figured I would mirror them here as well.
Edit: After a crash using the change name function and rebooting I don't have the crying dolphin anymore, maybe it's just because I switched from bt screen sharing to an android qflipper instance to usb linux qflipper it's a different screen idk. My screen is broken, so I need to use some form of display forwarding to use my fz.

@GameLord2011
Copy link
Contributor Author

GameLord2011 commented Sep 25, 2024 via email

@GameLord2011
Copy link
Contributor Author

GameLord2011 commented Sep 25, 2024 via email

@GameLord2011
Copy link
Contributor Author

GameLord2011 commented Sep 25, 2024 via email

@GameLord2011
Copy link
Contributor Author

GameLord2011 commented Sep 25, 2024 via email

@GameLord2011
Copy link
Contributor Author

GameLord2011 commented Sep 25, 2024 via email

@Helios343
Copy link

Helios343 commented Sep 26, 2024 via email

@Willy-JL Willy-JL added duplicate This issue or pull request already exists and removed needs-more-info Requires more information to triage labels Sep 27, 2024
@GameLord2011
Copy link
Contributor Author

GameLord2011 commented Sep 28, 2024 via email

@Willy-JL
Copy link
Member

Willy-JL commented Oct 1, 2024

Which is what happens?

@GameLord2011
Copy link
Contributor Author

GameLord2011 commented Oct 1, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

5 participants