Bug 40044 - ARM64: Memory Corruption (with awaiter)
Summary: ARM64: Memory Corruption (with awaiter)
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: iOS
Classification: Xamarin
Component: Mono runtime / AOT compiler ()
Version: master
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Zoltan Varga
URL:
Depends on:
Blocks:
 
Reported: 2016-04-01 09:41 UTC by Virgile Bello
Modified: 2016-04-04 03:46 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Repro project (8.45 KB, application/x-zip-compressed)
2016-04-01 09:41 UTC, Virgile Bello
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NOT_REPRODUCIBLE

Description Virgile Bello 2016-04-01 09:41:36 UTC
Created attachment 15585 [details]
Repro project

Attached a simple repro project: it creates a custom Awaiter and stores it in queue/pool.

It usually result in a crash during GC (repro project contains a few GC.Collect(0) to help it trigger early).
Comment 1 Virgile Bello 2016-04-01 09:42:57 UTC
Also, it happens with ARM64 but not ARMv7.
Comment 2 Virgile Bello 2016-04-04 03:46:23 UTC
Tested against the latest stable version released march 31st and it seems fixed (had this problem during the last 8 months, so I was surprised that a minor release might have fixed it).

I will reopen if it happens again.