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

[CP] Ensure CpuInfo Windows flag detection works, doesn't crash on pre-sse41 cpus #55211

Closed
aam opened this issue Mar 16, 2024 · 8 comments
Closed
Assignees
Labels
area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). cherry-pick-approved Label for approved cherrypick request cherry-pick-merged Cherry-pick has been merged to the stable or beta branch. cherry-pick-review Issue that need cherry pick triage to approve merge-to-beta merge-to-stable

Comments

@aam
Copy link
Contributor

aam commented Mar 16, 2024

Commit(s) to merge

c5946a1

Target

both

Prepared changelist for beta/stable

https://dart-review.googlesource.com/c/sdk/+/357983
https://dart-review.googlesource.com/c/sdk/+/358040

Issue Description

CPU detection wasn't working correctly on Windows, caused crashes of dart and flutter apps when running on older pre-sse41 cpus.

What is the fix

Ensure information about detected cpu features is properly used on Windows.

Why cherry-pick

Fix flutter and dart crashes for Windows users who also use older machines.

Risk

low

Issue link(s)

flutter/flutter#140138, flutter/flutter#138784, flutter/flutter#138693

Extra Info

No response

@aam aam added the cherry-pick-review Issue that need cherry pick triage to approve label Mar 16, 2024
@mit-mit
Copy link
Member

mit-mit commented Mar 18, 2024

SGTM

@mit-mit mit-mit added the area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). label Mar 18, 2024
@itsjustkevin itsjustkevin added cherry-pick-approved Label for approved cherrypick request merge-to-beta labels Mar 19, 2024
@itsjustkevin
Copy link
Contributor

@aam this CL is still showing errors on both beta and stable. Are these expected?

@aam
Copy link
Contributor Author

aam commented Mar 19, 2024

@itsjustkevin yeah, errors are unrelated and are expected: one set of failures are due to #55212 that recently affected infra, another - due to #55212 which is caused test failures due to transition from PST to PDT.

@itsjustkevin
Copy link
Contributor

Thanks @aam please go ahead and submit if that is the case.

copybara-service bot pushed a commit that referenced this issue Mar 19, 2024
BUG=flutter/flutter#140138
BUG=flutter/flutter#138784
BUG=flutter/flutter#138693
TEST=manually on win x64 with `__ int3();` added in front of `roundsd` and forced `CpuId::sse41=false;`

Cherry-pick: https://dart-review.googlesource.com/c/sdk/+/357218
Cherry-pick-request: #55211
Change-Id: I90a60d4972c5183d43516c628b68a71b7cc76912
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/357983
Reviewed-by: Siva Annamalai <asiva@google.com>
Commit-Queue: Alexander Aprelev <aam@google.com>
copybara-service bot pushed a commit that referenced this issue Mar 19, 2024
BUG=flutter/flutter#140138
BUG=flutter/flutter#138784
BUG=flutter/flutter#138693
TEST=manually on win x64 with `__ int3();` added in front of `roundsd` and forced `CpuId::sse41=false;`
Change-Id: I9e2dbf2615549dcc7c979036b5442276c2e0fb29
Cherry-pick: https://dart-review.googlesource.com/c/sdk/+/357218
Cherry-pick-request: #55211
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/358040
Reviewed-by: Siva Annamalai <asiva@google.com>
Commit-Queue: Alexander Aprelev <aam@google.com>
@aam
Copy link
Contributor Author

aam commented Mar 19, 2024

Submitted.

@itsjustkevin itsjustkevin added cherry-pick-merged Cherry-pick has been merged to the stable or beta branch. merge-to-stable labels Mar 20, 2024
@FifoTheHein
Copy link

This issue seems to be back in Flutter 3.22.X. Anyone else experiencing this? Reverting back to 3.19.6 resolves it again.

@itsjustkevin
Copy link
Contributor

@FifoTheHein if you’re seeing an issue, please open a new one. We do not review closed issues when triaging.

@helgoboss
Copy link

@FifoTheHein If you create a new issue, could you please post a link to it here? If this issue is really back (I hope not), I would like to subscribe to it ;) Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). cherry-pick-approved Label for approved cherrypick request cherry-pick-merged Cherry-pick has been merged to the stable or beta branch. cherry-pick-review Issue that need cherry pick triage to approve merge-to-beta merge-to-stable
Projects
None yet
Development

No branches or pull requests

8 participants