Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-20 06:33:42 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #5649] [BUG]: Android Mobile App: Context Initialization Failure & Excessive Cache Accumulation #5216

New Issue
Closed
opened 2026-06-05 14:52:42 -04:00 by yindo · 1 comment
yindo commented 2026-06-05 14:52:42 -04:00
Owner
Copy Link
Copy Source

Originally created by @hubertprus on GitHub (May 18, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5649

How are you running AnythingLLM?

Docker (local)

What happened?

Context Initialization Failure: After selecting and downloading the local Gemma model, the app consistently throws a critical error: "Failed to initialize context... Please check if the model file exists and is accessible." The application appears to lose the local file paths or lacks proper file permissions to access its own downloaded models.
Storage Bloat: The application accumulated nearly 1 GB of unmanaged data (~692 MB of orphaned data/cache) in a short period. The app became completely unresponsive, requiring a hard manual system data wipe to restore basic functionality.
Steps to Reproduce
Install the AnythingLLM Android app.
Select and download a local LLM (e.g., Gemma).
Attempt to initialize the chat interface.
Observe the context initialization failure.
Check Android app storage settings to find massive data accumulation with no internal way to clear it.
Expected Behavior
The app should maintain persistent and correct access to local model storage paths without losing file contexts. Furthermore, it should properly manage database sizes and prevent sudden, massive storage bloat.
Environment
Device: Android Smartphone
App Version: Latest Mobile Release
Testing Entity: Vertex Quant Tech Team
Thank you for your hard work on this amazing project. We hope this feedback helps the dev team optimize the mobile client!

Are there known steps to reproduce?

No response

LLM Provider & Model (if applicable)

No response

Embedder Provider & Model (if applicable)

No response

Originally created by @hubertprus on GitHub (May 18, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5649 ### How are you running AnythingLLM? Docker (local) ### What happened? Context Initialization Failure: After selecting and downloading the local Gemma model, the app consistently throws a critical error: "Failed to initialize context... Please check if the model file exists and is accessible." The application appears to lose the local file paths or lacks proper file permissions to access its own downloaded models. Storage Bloat: The application accumulated nearly 1 GB of unmanaged data (~692 MB of orphaned data/cache) in a short period. The app became completely unresponsive, requiring a hard manual system data wipe to restore basic functionality. Steps to Reproduce Install the AnythingLLM Android app. Select and download a local LLM (e.g., Gemma). Attempt to initialize the chat interface. Observe the context initialization failure. Check Android app storage settings to find massive data accumulation with no internal way to clear it. Expected Behavior The app should maintain persistent and correct access to local model storage paths without losing file contexts. Furthermore, it should properly manage database sizes and prevent sudden, massive storage bloat. Environment Device: Android Smartphone App Version: Latest Mobile Release Testing Entity: Vertex Quant Tech Team Thank you for your hard work on this amazing project. We hope this feedback helps the dev team optimize the mobile client! ### Are there known steps to reproduce? _No response_ ### LLM Provider & Model (if applicable) _No response_ ### Embedder Provider & Model (if applicable) _No response_
yindo added the possible bugneeds info / can't replicateOS: Mobile labels 2026-06-05 14:52:42 -04:00
yindo closed this issue 2026-06-05 14:52:42 -04:00
yindo commented 2026-06-05 14:52:43 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 19, 2026):

The application accumulated nearly 1 GB of unmanaged data (~692 MB of orphaned data/cache) in a short period. The app became completely unresponsive, requiring a hard manual system data wipe to restore basic functionality.

This seems odd - are you like cancelling the download of models during download or closing the app? All data is written to the same directory so I cannot yet be sure how/why what this data is. Does the file system say or indicate what type of files these things are?

The error simplify indicates it never finished downloading all the files needed to run a model, but it just uses the standard app-level directory for storage - nothing crazy or special permissions.

The application accumulated nearly 1 GB of unmanaged data (~692 MB of orphaned data/cache) in a short period.

Where/how did you get this information that it was orphaned or cache data? If you have access to that it would make sense you should be able to see what that data was?

<!-- gh-comment-id:4492461690 --> @timothycarambat commented on GitHub (May 19, 2026): > The application accumulated nearly 1 GB of unmanaged data (~692 MB of orphaned data/cache) in a short period. The app became completely unresponsive, requiring a hard manual system data wipe to restore basic functionality. This seems odd - are you like cancelling the download of models during download or closing the app? All data is written to the same directory so I cannot yet be sure how/why what this data is. Does the file system say or indicate what type of files these things are? The error simplify indicates it never finished downloading all the files needed to run a model, but it just uses the standard app-level directory for storage - nothing crazy or special permissions. > The application accumulated nearly 1 GB of unmanaged data (~692 MB of orphaned data/cache) in a short period. Where/how did you get this information that it was orphaned or cache data? If you have access to that it would make sense you should be able to see what that data was?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label OS: Mobile needs info / can't replicate possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#5216
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?