EnsureInitialized test crash on llvm19/iOS #105251
Assignees
Labels
area-Codegen-LLVM-mono
in-pr
There is an active PR which will close this issue when it is merged
Known Build Error
Use this to report build issues in the .NET Helix tab
os-ios
Apple iOS
Milestone
Comments
dotnet-issue-labeler
bot
added
the
needs-area-label
dotnet-policy-service
bot
added
the
untriaged
radekdoulik
added
area-Codegen-LLVM-mono
and removed
needs-area-label
|
Tagging subscribers to this area: @lambdageek, @steveisok |
|
So I just had this exact same crash on an iOS device on my PR. It happened on the device attached to DNCENGMAC048 which is an iPhone XR according to dcneng. That's a bit older and has an Apple A12 Bionic CPU, so maybe for some reason we're generating some instruction that the CPU doesn't like? The queue also has iPhone SE 2nd Gen devices on it which have a newer A13 CPU so maybe that's why we're not seeing the crash all the time? We definitely have a passing run on an iPhone SE. |
|
The Apple TV HD devices we have also use an older Apple A8 CPU. |
matouskozak
changed the title
matouskozak
added
os-ios
|
I was able to reproduce this on my old iPad Mini 4. It crashes with a SIGBUS on this instruction: I checked and the address in x8 is not aligned on an 8 byte boundary. I reduced the code down to this: private static int counter = 0;
private static void OnButtonClick()
{
object aLock = null;
Interlocked.CompareExchange(ref aLock, new object(), null);
string s = (counter++).ToString();
}When I just touch the code slightly like moving the counter++ to its own line (i.e. counter++ followed by counter.ToString) then the crash goes away. Here's the bitcode diff between the two versions: After talking to @lambdageek he thinks it's a codegen bug:
|
|
@akoeplinger I can reproduce the same crash on an iphone 8 and an XS Max. |
dotnet-policy-service
bot
added
the
in-pr
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Context: #103585 (comment)
Occasional failures in
System.Runtime.Testsonios_arm64_release_allsubsets_monojob.Known Issue Error Message
Fill the error message using step by step known issues guidance.
{ "ErrorMessage": "at System.Threading.LazyInitializer:EnsureLockInitialized", "BuildRetry": false, "ExcludeConsoleLog": false }Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=765139
Error message validated:
[at System.Threading.LazyInitializer:EnsureLockInitialized]Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 8/5/2024 7:51:08 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: