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

"Not enough memory to finish analysis" - add more details to message that it is RAM memory #12

Open
olekstomek opened this issue Feb 1, 2024 · 0 comments

Comments

@olekstomek
Copy link

Not enough memory to finish analysis. Please try closing a few application before re-running the analysis.

My proposal is to change this message that the problem is with RAM memory (to be clarify that it is not about ROM but I know that second part of this communicate about closing a few apps suggest that it is RAM). So, better it could be more precise:

Not enough RAM memory to finish analysis. Please try closing a few application before re-running the analysis.

The application showed this message right after updating Android while the OS was starting in the background. Perhaps it would be best to handle such a case by waiting until there is more RAM?

Screenshot_20240124_232537_SnoopSnitch

BTW, I don't know why this String doesn't exist in https://github.com/srlabs/snoopsnitch/blob/master/SnoopSnitch/app/src/main/res/values/strings.xml I didn't find it in other folders. Maybe this is outdated version because https://opensource.srlabs.de/projects/snoopsnitch/repository/snoopsnitch/revisions/8ce1c19f90f5b6e15e646a1773f691338090c949/entry/SnoopSnitch/app/src/main/res/values/strings.xml#L497 here this String exist:
<string name="patchalyzer_error_out_of_memory">Not enough memory to finish analysis. Please try closing a few applications before re-running the analysis.</string>
https://opensource.srlabs.de/projects/snoopsnitch/repository/snoopsnitch/revisions/8ce1c19f90f5b6e15e646a1773f691338090c949/diff/SnoopSnitch/app/src/main/res/values/strings.xml

Second part of this issue related to issues: #5 and #10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant