Add nullptr check for processor in QueryCacheParams. - #376
Merged
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
copybara-service
Bot
force-pushed
the
test_952009981
branch
from
July 22, 2026 11:04
287b4fc to
e241abb
Compare
When calling cpuinfo_get_processor(i), it can return nullptr on certain Android devices (e.g. Xiaomi, Oppo). When processor is null, accessing processor->cache causes a fatal SIGSEGV during ruy::CpuInfo::Initialize(). This change adds a null guard for processor in QueryCacheParams to ensure it is skipped, allowing safe fallback to default cache parameters if detection fails. PiperOrigin-RevId: 952022058
copybara-service
Bot
force-pushed
the
test_952009981
branch
from
July 22, 2026 11:05
e241abb to
857bcab
Compare
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
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.
Add nullptr check for processor in QueryCacheParams.
When calling cpuinfo_get_processor(i), it can return nullptr on certain Android devices (e.g. Xiaomi, Oppo). When processor is null, accessing processor->cache causes a fatal SIGSEGV during ruy::CpuInfo::Initialize().
This change adds a null guard for processor in QueryCacheParams to ensure it is skipped, allowing safe fallback to default cache parameters if detection fails.