Bug 56925 - Fatal signal 6 (sigabrt)
Summary: Fatal signal 6 (sigabrt)
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.3.5
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Paul DiPietro [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2017-05-29 08:48 UTC by Alessandro
Modified: 2017-06-20 18:10 UTC (History)
3 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 NOT_REPRODUCIBLE

Description Alessandro 2017-05-29 08:48:42 UTC
I have an Entry. When Entry got focus, a Keyboard appears.
If I presso "done" button, I have this

Resolved pending breakpoint at 'PagePassword.cs:35,1' to void Fev.Pages.PagePassword.<>c__DisplayClass6_0.<<-ctor>b__0>d.MoveNext () [0x0001a].
[] * Assertion at /Users/builder/data/lanes/4695/bc246455/source/xamarin-android/external/mono/mono/mini/debugger-agent.c:8949, condition `locals->locals [i].index < header->num_locals' not met
[libc] Fatal signal 6 (SIGABRT) at 0x00002312 (code=-6), thread 9006 (t.esselunga.fev)

Tested on Android 4.4.3

Xamarin.Android 7.3
Comment 1 Alessandro 2017-05-29 09:00:37 UTC
with X.F. 2.3.4 I have not this problem
Comment 2 Paul DiPietro [MSFT] 2017-05-29 17:13:11 UTC
Please upload a reproduction when you have a chance.
Comment 3 Alessandro 2017-06-16 12:08:06 UTC
I have had this problem only on a device... when I will have that device in my hands I will try to reproduce the problem
Comment 4 Paul DiPietro [MSFT] 2017-06-20 18:10:57 UTC
We are setting this to resolved/not reproducible as we don't have a reproduction to work with at the moment. If you find this issue is still occurring on the latest prerelease or nightly builds and can provide a minimized reproduction project, please reopen this and attach the project. Thanks!