Repository navigation
iOS: Attempting to JIT compile method '(wrapper dynamic-method) string object:lambda_method1 (System.Runtime.CompilerServices.Closure)' while running in aot-only mode. #47112
Description
Description
The following code throws an exception at runtime when running on an iOS device:
var foos = new string [] { "hi", "bye" };
string f = foos.AsQueryable ().First ();Exception:
System.ExecutionEngineException: Attempting to JIT compile method '(wrapper dynamic-method) string object:lambda_method1 (System.Runtime.CompilerServices.Closure)' while running in aot-only mode. See https://docs.microsoft.com/xamarin/ios/internals/limitations for more information.
at System.Delegate.CreateDelegate(Type type, Object firstArgument, MethodInfo method, Boolean throwOnBindFailure, Boolean allowClosed)
at System.Delegate.CreateDelegate(Type type, Object firstArgument, MethodInfo method, Boolean throwOnBindFailure)
at System.Delegate.CreateDelegate(Type type, Object firstArgument, MethodInfo method)
at System.Reflection.Emit.DynamicMethod.CreateDelegate(Type delegateType, Object target)
at System.Linq.Expressions.Compiler.LambdaCompiler.CreateDelegate()
at System.Linq.Expressions.Compiler.LambdaCompiler.Compile(LambdaExpression lambda)
at System.Linq.Expressions.Expression`1[[System.Func`1[[System.String, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Compile()
at System.Linq.EnumerableExecutor`1[[System.String, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Execute()
at System.Linq.EnumerableQuery`1[[System.String, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].System.Linq.IQueryProvider.Execute[String](Expression expression)
at System.Linq.Queryable.First[String](IQueryable`1 source)
at MySingleView.AppDelegate.FinishedLaunching(UIApplication app, NSDictionary options) in /Users/rolf/work/maccore/onedotnet/xamarin-macios/tests/dotnet/MySingleView/AppDelegate.cs:line 27Repro:
git clone https://github.com/rolfbjarne/xamarin-macios
cd xamarin-macios
git checkout dotnet-attempting-to-jit-compile-method-lamba_method1
./configure --enable-dotnet
make reset
make all -j8
make install -j8
make mysingleview -C tests/dotnetConfiguration
.NET 6.0.100-alpha.1.21060.3
Binlog:
MySingleView.binlog.zip
Regression?
No (new feature)
Activity
EgorBo commentedon Jan 18, 2021
I suspect
LambdaCompilershould always prefer interpretation instead of compilation on iOS.https://github.com/dotnet/runtime/blob/master/src/libraries/System.Linq.Expressions/src/System.Linq.Expressions.csproj#L6-L9
steveisok commentedon Jun 28, 2021
@MaximLipnin See if you can reproduce and give Egor's suggestion a try after.
MaximLipnin commentedon Jun 29, 2021
I faced a lot of library test failures with similar error in in #50510. I have no any ios device at hand so I'll try re-enabling System.Linq.Expresions test suite in the PR and see any related CI failures.
steveisok commentedon Jun 29, 2021
@MaximLipnin try testing against the simulator with aot enabled. You should be able to take Rolf's example and alter the functional test to repro.
MaximLipnin commentedon Jun 30, 2021
It's reproducible against the simulator when executing
@EgorBo What would be the right way to apply your suggestion? When trying to set
<IsInterpreting>true</IsInterpreting>I get the following error:
The
System.Linq.Expressions.ExpressionCreatortype is not in the reference assembly.steveisok commentedon Jun 30, 2021
@ViktorHofer Not quite sure who to ask, but would you happen to know the answer to Maxim's question?
EgorBo commentedon Jun 30, 2021
@MaximLipnin I guess nobody tested "true" for that condition and it doesn't expose the same public APIs when it's set.
if the only error AppCompat found is
that should not be difficult to fix
ViktorHofer commentedon Jun 30, 2021
Right, we had that option enabled on some configurations (I believe uap) which don't exist anymore. Nobody noticed that the API surface diverged when using the interpreter mode.
Make LambdaCompiler prefer interpretation to compilation on iOS (#54970)