Bug 32007 - sgen error "error: no object of size 859338152"
Summary: sgen error "error: no object of size 859338152"
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Runtime
Classification: Mono
Component: GC ()
Version: unspecified
Hardware: PC Mac OS
: Normal normal
Target Milestone: (C6SR1)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-07-16 06:05 UTC by Alan McGovern
Modified: 2015-11-09 11:46 UTC (History)
6 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 GitHub or Developer Community 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 Alan McGovern 2015-07-16 06:05:58 UTC
I got this when running xs/master using the latest mono 4.2 pre2:


2015-07-16 10:56:39.996 mono-sgen[39077:2575150] error: no object of size 859338152
Stacktrace:

  at <unknown> <0xffffffff>
  at (wrapper managed-to-native) object.__icall_wrapper_mono_array_new_specific (intptr,int) <IL 0x00026, 0xffffffff>
  at System.Collections.Generic.List`1<ICSharpCode.NRefactory.Utils.FastSerializer/CustomDeserialization>.set_Capacity (int) [0x0002a] in /private/tmp/source-mono-mac-4.2.0-pre2-branch/bockbuild-mono-4.2.0-pre2-branch/profiles/mono-mac-xamarin/build-root/mono-4.2.0/external/referencesource/mscorlib/system/collections/generic/list.cs:132
  at System.Collections.Generic.List`1<ICSharpCode.NRefactory.Utils.FastSerializer/CustomDeserialization>.EnsureCapacity (int) [0x00046] in /private/tmp/source-mono-mac-4.2.0-pre2-branch/bockbuild-mono-4.2.0-pre2-branch/profiles/mono-mac-xamarin/build-root/mono-4.2.0/external/referencesource/mscorlib/system/collections/generic/list.cs:446
  at System.Collections.Generic.List`1<ICSharpCode.NRefactory.Utils.FastSerializer/CustomDeserialization>.Add (ICSharpCode.NRefactory.Utils.FastSerializer/CustomDeserialization) [0x00013] in /private/tmp/source-mono-mac-4.2.0-pre2-branch/bockbuild-mono-4.2.0-pre2-branch/profiles/mono-mac-xamarin/build-root/mono-4.2.0/external/referencesource/mscorlib/system/collections/generic/list.cs:249
Comment 1 Mark Probst 2015-09-25 12:28:23 UTC
How can we reproduce this?
Comment 2 Alan McGovern 2015-09-25 12:51:42 UTC
It's a random failure. The same sort of random failure is triggered when compiling the fsharp submodule in the monodevelop checkout, however it's reasonably rare. I've seen it about a dozen times over the last few hundred builds.

A repro would be to constantly clean and rebuild the fsharp submodule after you've checked out monodevelop/master
Comment 3 Miguel de Icaza [MSFT] 2015-09-25 13:04:52 UTC
This has been reported in the past:

https://bugzilla.xamarin.com/show_bug.cgi?id=11322

Also in NRefactory.
Comment 4 Mark Probst 2015-09-29 13:42:22 UTC
Can you give me wrench links to Mono and XamMac builds that reproduce this?
Comment 5 Alan McGovern 2015-09-29 14:02:56 UTC
Use XS to install the current alpha builds. That's the simplest option
Comment 6 Mark Probst 2015-10-01 13:49:05 UTC
"Error retrieving update information."
Comment 7 PJ 2015-10-02 15:41:50 UTC
No information is still requested -> ASSIGNED. 

I don't think Mark is actually stuck, but maybe he can clarify with more words.
Comment 8 Mark Probst 2015-10-02 18:03:31 UTC
That's what I get when I try to switch XS to Alpha - "Error retrieving update information."
Comment 9 PJ 2015-10-02 18:10:19 UTC
You might be hitting something like bug 27237 or bug 14845, but I'm not sure without more information. Here are the latest Alpha builds from the last release thread update for C6:

	Mono 4.2.1.56
		http://storage.bos.internalx.com/mono-mac-4.2.0-branch/4a/4a18c575ac105b920ec7fb37b24ffe74ad9b3bd7/MonoFramework-MDK-4.2.1.56.macos10.xamarin.x86.pkg
		MD5: 7c29f53a2fee4cbec39fa5ee7ca11f92

	XA 6.0.0.2
		http://storage.bos.internalx.com/monodroid-mavericks-cycle6/53/537132d65e8e9f2f7e681ccfd126ace009cb90e5/mono-android-6.0.0-2.pkg
		MD5: 8b54a8343241a6a3b6df54e91e5c3254

	XI 9.2.0.67
		http://storage.bos.internalx.com/macios-mac-cycle6/f8/f85a8459fbce312f6b35f77891e773f50086aa8b/monotouch-9.2.0.67.pkg
		MD5: 08b7bc6772d1b37a3e3efa2cb878d72b

	XM 2.4.0.62
		http://storage.bos.internalx.com/macios-mac-cycle6/f8/f85a8459fbce312f6b35f77891e773f50086aa8b/xamarin.mac-2.4.0.62.pkg
		MD5: e44db73a6061e92b2322cddd0ef3f67f

	XS 5.10.0.800
		http://storage.bos.internalx.com/monodevelop-lion-cycle6/92/92083188182e8c4588153e0d63e99c1a7037e4b6/XamarinStudio-5.10.0.800.dmg
		MD5: 8864a87f586a0d01b2bc715c8aeb3493

		http://storage.bos.internalx.com/monodevelop-windows-cycle6/92/92083188182e8c4588153e0d63e99c1a7037e4b6/XamarinStudio-5.10.0.800.msi
		MD5: 49bfd1f0b8ae4c1edd0428310f27e690

	XVS 4.0.0.1505
		http://storage.bos.internalx.com/xvs-win-cycle6/9a/9ac5fb836b43036a674d91a139796e38c3ad5139/Xamarin.VisualStudio_4.0.0.1505.msi
		MD5: 4a2a05abb3b9db913d72f829f741c2c2
		
	GTK# 2.12.30
		http://files.xamarin.com/~duncan/gtk-sharp-2.12.30.msi
		MD5: de32be72330bc4599964be3ca7a462b2

Those builds are the current Alpha.
Comment 11 Mark Probst 2015-10-21 12:34:02 UTC
I've been trying to reproduce this on OSX with fsharpbinding 7ad9a882c37218041335b94fb9f0ca1b79614d4c, compiling with mono master (844fc33437baca1d2bd44558d58cc7a5bc918774) and fsharp31 branch (c5e345b194eaddad7f06d47cd944b098f3dbe325).

It's been running all night and not a single crash.  Is this still an issue?
Comment 12 PJ 2015-10-30 13:45:35 UTC
Alan any chance you can help Mark reproduce this?
Comment 13 PJ 2015-11-09 10:31:34 UTC
This was never reproducible in QA, and is not going to block the C6 release in it's current state. Updating milestone.
Comment 14 Alan McGovern 2015-11-09 11:46:30 UTC
There's no further information to provide.

If it can't be reproed i'll just close it.