[Mono-bugs] [Bug 687727] New: Mono for Android - Assertion at ../../../../mono/metadata/sgen-internal.c:441, condition `mh->size == size + sizeof (LargeInternalMemHeader)' not met
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Thu Apr 14 18:56:41 EDT 2011
https://bugzilla.novell.com/show_bug.cgi?id=687727
https://bugzilla.novell.com/show_bug.cgi?id=687727#c0
Summary: Mono for Android - Assertion at
../../../../mono/metadata/sgen-internal.c:441,
condition `mh->size == size + sizeof
(LargeInternalMemHeader)' not met
Classification: Mono
Product: Mono: Runtime
Version: 2.0.x
Platform: Other
OS/Version: Windows 7
Status: NEW
Severity: Critical
Priority: P5 - None
Component: misc
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: andrew at magic5software.com
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64;
Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729;
Media Center PC 6.0; InfoPath.2; FDM; OfficeLiveConnector.1.5;
OfficeLivePatch.1.3; .NET4.0C; .NET4.0E)
I'm getting the error:
Assertion at ../../../../mono/metadata/sgen-internal.c:441, condition `mh->size
== size + sizeof (LargeInternalMemHeader)' not met
when running an application on a Samsung Galaxy S, Android 2.2 using Mono for
Android 1.0.0.10192. The error is reported back to the host PC adb log. This
causes the application to fail, and debugging cannot be stopped. The problem
also happens in a non-debug scenario, so I'm very worried that this might be an
issue with production applications produced with Mono for Android.
The error happens seemingly randonly after using the application for an amount
of time (eg. 1 or 2 minutes).
I can't reproduce the problem other than by using the application and waiting
for it to fail.
Details of my e-mail to the MonoDroid mailing list are here:
------------
I’m seeing this error as well:
Assertion at ../../../../mono/metadata/sgen-internal.c:441, condition `mh->size
== size + sizeof (LargeInternalMemHeader)' not met
It’s not a predictable one – sometimes it occurs when setting up views within
an activity (in particular it happened once within BitmapFactory.DecodeFile,
but running that function 1000 times on the same file worked fine.)
I’ve also seen it occur in a background thread somewhere within a series of
Http requests and associated database access.
The symptoms in both cases are the same – the device screen goes blank and it’s
not possible to stop a debugging session from within VS. The error also happens
when the app isn’t running through the debugger. The same areas of the
application work fine at other times.
The message logged is the one above, it gets tagged with the same tag as my
previous logging call, if that’s of any significance.
I’ll log this even though I don’t have a reproducible test case, I imagine it’s
a bit of a fundamental one, with the app randomly crashing here and there.
Is there likely to be anything that can be done from the app side to work
around this?
Thanks,
Andy
--------------
The same error has been reported on the list by another user:
-----------------
Hi,
somtimes when starting an activity i get the following error:
04-01 18:34:53.724 1321 1344 I ActivityManager: Displayed activity
CSMobile.UI/csmobile.ui.forms.sql.co.Main: 301 ms (total 301 ms)
04-01 18:34:54.451 1321 1458 I ActivityManager: Starting activity: Intent {
cmp=CSMobile.UI/csmobile.ui.forms.sql.Email }
04-01 18:34:54.505 13752 13752 I monodroid: Activating instance of type
CSMobile.UI.Forms.Sql.Email
04-01 18:34:54.505 13752 13752 I monodroid: signature
04-01 18:34:54.505 13752 13752 I monodroid: Activating instance of type
CSMobile.UI.Controls.CSHeader
04-01 18:34:54.505 13752 13752 I monodroid: signature Android.Content.Context,
Mono.Android, Version=0.0.0.0, Culture=neutral,
PublicKeyToken=null:Android.Util.IAttributeSet, Mono.Android, Version=00.0.0,
Culture=neutral, PublicKeyToken=null
04-01 18:34:54.513 13752 13752 I monodroid: Activating instance of type
CSMobile.UI.Controls.CSHorizontalScrollView
04-01 18:34:54.513 13752 13752 I monodroid: signature Android.Content.Context,
Mono.Android, Version=0.0.0.0, Culture=neutral,
PublicKeyToken=null:Android.Util.IAttributeSet, Mono.Android, Version=00.0.0,
Culture=neutral, PublicKeyToken=null
04-01 18:34:54.521 13752 13752 I monodroid: Activating instance of type
CSMobile.UI.Controls.CSList
04-01 18:34:54.521 13752 13752 I monodroid: signature Android.Content.Context,
Mono.Android, Version=0.0.0.0, Culture=neutral,
PublicKeyToken=null:Android.Util.IAttributeSet, Mono.Android, Version=00.0.0,
Culture=neutral, PublicKeyToken=null
04-01 18:34:54.654 13752 13752 F mono : * Assertion at
./../../../mono/metadata/sgen-internal.c:441, condition `mh->size == size +
sizeof (LargeInternalMemHeader)' not met
04-01 18:35:00.013 1321 1329 D KeyguardUpdateMonitor: received broadcast
android.intent.action.TIME_TICK
04-01 18:35:00.013 1321 1346 D KeyguardUpdateMonitor: handleTimeUpdate
04-01 18:35:04.459 1321 1333 W ActivityManager: Launch timeout has expired,
giving up wake lock!
04-01 18:35:04.506 1321 1333 W ActivityManager: Activity idle timeout for
HistoryRecord{45da59b8 CSMobile.UI/csmobile.ui.forms.sql.Email}
Any Idea what that means?
Thanks for your help.
Bernhard Gessler
--------------
Reproducible: Always
Steps to Reproduce:
1. I can reproduce the problem by using my application, but I don't have a set
of steps that will lead to the error - continued use for a few minutes seems to
end up with the error.
2.
3.
Actual Results:
Application freezes on the Android device, black screen shown, no response.
Debugging (if it was in progress) cannot be stopped without killing the visual
studio process.
Expected Results:
Not generated the error ideally!
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list