Bug 180 - Occasional hard-crashes during allocation.
Summary: Occasional hard-crashes during allocation.
Status: RESOLVED INVALID
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 4.x
Hardware: Other Other
: --- major
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-08-04 10:59 UTC by Dean Herbert
Modified: 2011-08-10 09:24 UTC (History)
2 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 INVALID

Description Dean Herbert 2011-08-04 10:59:18 UTC
I can't reproduce this on my iOS hardware, but have had it reported by testers (3GS/3G, though I'm not sure that is related). The code where it occurred in this case is:

NSMutableUrlRequest req = new NSMutableUrlRequest(new NSUrl(UrlEncode(m_url)), NSUrlRequestCachePolicy.ReloadIgnoringCacheData, 30);
req.HttpMethod = method; //method is "POST" in this case

The crash log contains:

  1 sigabrt_signal_handler (in osustream) (mini-posix.c:195)
  2 0x330f3728
  3 0x330e83b4
  4 0x330e0bf8
  5 GC_remap (in osustream) (os_dep.c:2092)
  6 GC_allochblk_nth (in osustream) (allchblk.c:730)
  7 GC_allochblk (in osustream) (allchblk.c:561)
  8 GC_new_hblk (in osustream) (new_hblk.c:253)
  9 GC_allocobj (in osustream) (alloc.c:1116)
 10 GC_generic_malloc_inner (in osustream) (malloc.c:136)
 11 GC_generic_malloc (in osustream) (malloc.c:192)
 12 GC_malloc (in osustream) (malloc.c:297)
 13 mono_object_allocate (in osustream) (object.c:4204)
 14 mono_array_new_specific (in osustream) (object.c:4786)
 15 mono_custom_attrs_construct_by_type (in osustream) (reflection.c:8415)
 16 mono_reflection_get_custom_attrs_by_type (in osustream) (reflection.c:8880)
 17 custom_attrs_get_by_type (in osustream) (icall.c:7517)
 18 wrapper_managed_to_native_System_MonoCustomAttrs_GetCustomAttributesInternal_System_Reflection_ICustomAttributeProvider_System_Type_bool (in osustream) + 84
 19 mscorlib_System_MonoCustomAttrs_GetCustomAttributes_System_Reflection_ICustomAttributeProvider_System_Type_bool (in osustream) + 120
 20 mscorlib_System_MonoCustomAttrs_GetCustomAttribute_System_Reflection_ICustomAttributeProvider_System_Type_bool (in osustream) + 16
 21 mscorlib_System_Attribute_GetCustomAttribute_System_Reflection_MemberInfo_System_Type_bool (in osustream) + 36
 22 monotouch_MonoTouch_ObjCRuntime_Class_GetHandle_System_Type (in osustream) + 4
 23 monotouch_MonoTouch_Foundation_NSObject_AllocIfNeeded (in osustream) + 28
 24 monotouch_MonoTouch_Foundation_NSNumberFormatter_set_FormatterBehavior_MonoTouch_Foundation_NSNumberFormatterBehavior (in osustream) + 76
 25 monotouch_MonoTouch_Foundation_NSSet_TrampolineNSSetEnumerator_intptr_intptr_bool_ (in osustream) + 208
 26 monotouch_MonoTouch_Foundation_NSMutableUrlRequest_set_HttpMethod_string (in osustream) + 28
Comment 1 Rolf Bjarne Kvinge [MSFT] 2011-08-08 11:53:38 UTC
This looks very much like the app ran out of memory, and the fact that it only happens on older devices would suggest the same thing. Maybe you can instrument your own build and see if there are any memory leaks or some place you can use less memory?

Otherwise it's very hard for us to find any problems without a reprocible test case.
Comment 2 Dean Herbert 2011-08-08 11:55:08 UTC
Thanks for the clarification. I'll look into my memory usage and make sure I'm not leaking.
Comment 3 Rolf Bjarne Kvinge [MSFT] 2011-08-10 09:24:11 UTC
Closing bug for now, if you still have problems after checking your memory usage please reopen with a test case.