Bug 55934 - Many invalid-pointer crashes during automated tests on Intel32 FullAOT lanes
Summary: Many invalid-pointer crashes during automated tests on Intel32 FullAOT lanes
Status: NEW
Alias: None
Product: Runtime
Classification: Mono
Component: GC ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-05-03 20:23 UTC by Andi McClure
Modified: 2017-07-19 16:20 UTC (History)
3 users (show)

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

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 for Bug 55934 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Andi McClure 2017-05-03 20:23:38 UTC
The Intel32 FullAOT lane is displaying extensive crashes when running test-wrench on every build. See:


The crashes seem to appear in different places but all involve loading garbage pointers. Examples:

Failure in __icall_wrapper_mono_gc_alloc_obj
"Cannot access memory at address 0x5d"

Failure in System.Threading.Monitor.Exit
Cannot access memory at address 0x5

Failure in __icall_wrapper_mono_delegate_end_invoke
Cannot access memory at address 0x5

We are currently seeing some other FullAOT lane failures, including this Intel32-only error during fullaotcheck https://bugzilla.xamarin.com/show_bug.cgi?id=55931 which may be related; and a verification failure https://bugzilla.xamarin.com/show_bug.cgi?id=55932 on all lanes.

It might be this bug is in fact occurring on all lanes, but is being masked by this bug which is preventing make test-wrench from  running https://bugzilla.xamarin.com/show_bug.cgi?id=55933