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 1664 [details]
Stacktrace about error
When I run in debug an app on the simulator (by device everything works properly!) and I try to experiment on a control UIPickerView (I simply scroll of lines) the app crashes with error attached.
Why? It seems a problem of the debugger but I can not fix it.
Waiting for news Best regards.
Similar stack trace can occurs when the GC collects an object instance. Since the GC collection is called much more frequently on the simulator (to catch those cases) then it may not occur (often, but it could anytime) in devices.
Of course it could also be something else entirely... the stack trace is not complete enough to be sure of this.
Could you attach a test case that shows this behavior ? (mark it private if required). If we can duplicate the issue (along the the source) we should be able to pinpoint the crash origins. Thanks
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.