Bug 2091 - Assertion at ../../../../mono/metadata/sgen-bridge.c:426, condition `!entry->is_bridge' not met
Summary: Assertion at ../../../../mono/metadata/sgen-bridge.c:426, condition `!entry->...
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 1.9.2
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-11-18 13:18 UTC by andrew
Modified: 2011-12-08 03:20 UTC (History)
2 users (show)

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

adb log file showing assertion failure (3.61 KB, text/plain)
2011-11-18 13:18 UTC, andrew
Repro project (774.95 KB, application/x-zip-compressed)
2011-12-06 20:06 UTC, andrew

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 andrew 2011-11-18 13:18:19 UTC
Created attachment 908 [details]
adb log file showing assertion failure

I get the assertion failure:

Assertion at ../../../../mono/metadata/sgen-bridge.c:426, condition `!entry->is_bridge' not met

during routine app usage. It's not something that happens repeatably, it's just a random error that occurs and causes the app to lock up.

adb output attached - I'm pretty sure I've seen this before but not with the same stack trace.

I don't have a project which will be able to reliably produce this error. Is there anything I can do to help diagnose/debug it?
Comment 1 Rodrigo Kumpera 2011-11-23 18:36:18 UTC
Please provide an app that causes this crash with instructions on how to reproduce it.
It can be a reasonably big one as long as you can reproduce it with not a lot of manual interaction.

Without a way to reproduce it, it's very very hard to figure out what's wrong.
Comment 2 andrew 2011-12-01 18:36:37 UTC
I think I have a reliable way of reproducing this one.

I'll aim to package it up and get it over to you.
Comment 3 Rodrigo Kumpera 2011-12-05 05:58:23 UTC
Hi Andrew,

Those are great news! Thanks for taking the time producing a test for this bug.

It works to have any sample that crashes it as long as the crash is as reliable as possible.
Comment 4 andrew 2011-12-06 20:05:18 UTC
I'm attaching a project which shows this error. In the project I create some linear layouts in a loop (up to 100 times) and, for each layout, add in 20 text views, each of which is populated with text from a big embedded XML string.

I know this is artificial but it does generate the same error as I've seen many tmies now with 4.0 and my real application.

Although 100 layouts can be created, this repro consistently fails for me on the 12th layout. Testing on a Galaxy S.

To reproduce, run GCBugTester, tap on the button on the first screen, then tap on the "lots of views" button on the next. You'll see in the adb log it shows which layout it is creating, hopefully after a few seconds you'll see the crash.

Let me know if you need anything else.

Comment 5 andrew 2011-12-06 20:06:31 UTC
Created attachment 1007 [details]
Repro project

See previous comment for details.
Comment 6 Rodrigo Kumpera 2011-12-07 19:32:33 UTC
Fixed, will be part of our next Mono for Android stable release.
Comment 7 andrew 2011-12-08 03:20:55 UTC
Excellent, sounds good. I'm hoping the release will be soon!