Bug 12980 - SIGSEGV crash, combined use of Spinner and TimePickerDialog
Summary: SIGSEGV crash, combined use of Spinner and TimePickerDialog
Alias: None
Product: Android
Classification: Xamarin
Component: Pre-release ()
Version: 4.7.x
Hardware: PC Windows
: --- normal
Target Milestone: 4.8.x (post async)
Assignee: Rodrigo Kumpera
Depends on:
Reported: 2013-07-01 11:12 UTC by Arthur
Modified: 2013-10-18 11:29 UTC (History)
2 users (show)

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

Testcase with stacktrace (7.57 MB, application/octet-stream)
2013-07-01 11:56 UTC, Arthur

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:

Description Arthur 2013-07-01 11:12:06 UTC
Have an app developed with Xamarin.Droid, MvvmCross App contains a Spinner where user can select a time. Upon selecting a time, a TimePickerDialog will be show to change the selected time.

After 10+ (or more) times selecting another item and changing it's time, the app crashes with a SIGSEGV.
Comment 1 Arthur 2013-07-01 11:56:00 UTC
Created attachment 4243 [details]
Testcase with stacktrace
Comment 4 Jonathan Pryor 2013-10-18 11:29:37 UTC
I'm no longer able to reproduce with what will become the 4.10.x series (due in Alpha soon, I hope, assuming I'm not proven wrong in my release estimates yet again...).

Please try with with the 4.10 alpha (when available) and see if that fixes the issue for you. (Or try with 4.8.3, which I haven't tried.)