Merged
Conversation
ONNX Runtime loads models via mmap — the kernel pages data on demand, so low MemAvailable doesn't mean models can't load. The check was blocking Pixel 9 Pro users with 240MB reported available even though the device has 16GB physical RAM. Fixes #9
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/proc/meminfomemory check that was blocking Pixel 9 Pro usersmmapfor model loading — lowMemAvailabledoesn't mean models can't loadContext
Issue #9: Pixel 9 Pro (16GB RAM) reports 240MB available and throws
IllegalStateException. The device has plenty of physical RAM — the kernel just reports lowMemAvailablebecause it's used for caches/buffers.Test plan
Fixes #9