Bug 6704 - System.Exception: Attempting to JIT compile method
Summary: System.Exception: Attempting to JIT compile method
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 5.2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-08-27 10:23 UTC by Devaim
Modified: 2013-05-29 19:50 UTC (History)
2 users (show)

Tags:
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 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 NORESPONSE

Description Devaim 2012-08-27 10:23:25 UTC
I had this exception when i used *.ToList()


'System.Linq.jvm.Runner:GetDelegate<T,bool> ()' while running with --aot-only.
Comment 1 Sebastien Pouliot 2012-08-27 14:23:29 UTC
ToList works in most cases. You're likely running into one of the MonoTouch limitations wrt generics [1].

We'll need to complete, self contained test case (the details are very important), to see if this is fixed (5.3.x has many fixes) or not (work is on going on them). Thanks!

[1] http://docs.xamarin.com/ios/about/limitations
Comment 2 Sebastien Pouliot 2013-05-29 19:50:30 UTC
6.3.x beta releases have much improved to avoid this situation (the EngineExecutionException). You might want to try this, or similar code, again and report any remaining issues (with a test case).