Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 144 [details]
Sample for reproducing the issue
I've reproduced in a sample app a strange issue that I have with a generic function.
From the sample, the generic function Execute of ServiceExecutor class is called for two types of parameters (Request1 and Request2).
If the execute method is called about 10 times for one kind of parameter (Request1) and then is called for the other type (Request2) the app crashes, raising a System.ExecutionEngineException: SIGILL (I cannot get more specific info about the problem from the exception message).
I have this problem only when I use the app in a real device (I tested on iPad 1), while it works correctly on the simulator.
In order to reproduce it, just run the app in the device and click the only button about 11-12 times, it should crash.
If I use ServiceExecutor directly, without using a IServiceExecutor interface, it works too, but I'd like to use the interface.
I'm running MonoTouch 220.127.116.11.
I don't know if this issue http://bugzilla.xamarin.com/show_bug.cgi?id=60 can be caused by the same problem and if the same solution (in MT 4.1) can be applied.
With version 4.1 the problem seems to be solved!
Then it was likely the same issue. Thanks for testing and reporting this back to us!