Out of Memory in Xamarin Studio and Visual Studio for Mac

[JCKodel]

When building a Xamarin Forms project:

Error: Fody: An unhandled exception occurred:
Exception:
Out of memory
StackTrace:
  at (wrapper alloc) System.Object:AllocVector (intptr,intptr)
  at Microsoft.Cci.Pdb.MsfDirectory..ctor (Microsoft.Cci.Pdb.PdbReader reader, Microsoft.Cci.Pdb.PdbFileHeader head, Microsoft.Cci.Pdb.BitAccess bits) [0x000a5] in <d39e61ae2787473a851567b860d13696>:0 
  at Microsoft.Cci.Pdb.PdbFile.LoadFunctions (System.IO.Stream read, System.Collections.Generic.Dictionary`2[System.UInt32,Microsoft.Cci.Pdb.PdbTokenLine]& tokenToSourceMapping, System.String& sourceServerData, System.Int32& age, System.Guid& guid) [0x00027] in <d39e61ae2787473a851567b860d13696>:0 
  at Mono.Cecil.Pdb.PdbReader.PopulateFunctions () [0x00008] in <d39e61ae2787473a851567b860d13696>:0 
  at Mono.Cecil.Pdb.PdbReader.ProcessDebugHeader (Mono.Cecil.Cil.ImageDebugDirectory directory, System.Byte[] header) [0x00048] in <d39e61ae2787473a851567b860d13696>:0 
  at Mono.Cecil.ModuleDefinition.ProcessDebugHeader () [0x00012] in <b5a52cab1f0046ce9f68342127787868>:0 
  at Mono.Cecil.ModuleDefinition.ReadSymbols (Mono.Cecil.Cil.ISymbolReader reader) [0x00015] in <b5a52cab1f0046ce9f68342127787868>:0 
  at Mono.Cecil.ModuleReader.ReadSymbols (Mono.Cecil.ModuleDefinition module, Mono.Cecil.ReaderParameters parameters) [0x00047] in <b5a52cab1f0046ce9f68342127787868>:0 
  at Mono.Cecil.ModuleReader.CreateModuleFrom (Mono.Cecil.PE.Image image, Mono.Cecil.ReaderParameters parameters) [0x00076] in <b5a52cab1f0046ce9f68342127787868>:0 
  at Mono.Cecil.ModuleDefinition.ReadModule (System.IO.Stream stream, Mono.Cecil.ReaderParameters parameters) [0x00028] in <b5a52cab1f0046ce9f68342127787868>:0 
  at Mono.Cecil.ModuleDefinition.ReadModule (System.String fileName, Mono.Cecil.ReaderParameters parameters) [0x0000a] in <b5a52cab1f0046ce9f68342127787868>:0 
  at InnerWeaver.ReadModule () [0x00052] in <f6f9069078364b4db60945017a527c4a>:0 
  at InnerWeaver.Execute () [0x00019] in <f6f9069078364b4db60945017a527c4a>:0 
 ([Solution's Name])

It takes less than 2 seconds to crash. There is plenty of memory available:

Hardware Overview:

  Model Name:	iMac
  Model Identifier:	iMac14,2
  Processor Name:	Intel Core i7
  Processor Speed:	4,01 GHz
  Number of Processors:	1
  Total Number of Cores:	4
  L2 Cache (per Core):	256 KB
  L3 Cache:	8 MB
  Memory:	32 GB

[tuyen-vuduc]

I also face this issue. I logged an issue on a Realm repo.

[tuyen-vuduc]

Change .NET Runtime to v4.8 in Xamarin Studio/VS for Mac Preference will be a workaroud

[bbkillen]

kanvuduc's solution fixed my problem and saved my bacon!!!

[stefandevo]

I reported this on the mono. bugzilla

[stefandevo]

And now moved to jbevain/cecil#378 as Mono group is pointing to Cecil as the cause.

[stefandevo]

And now Cecil is pointing to Fody again jbevain/cecil#378 (comment).

Is Fody using v0.9 or v.10 ?

[stefandevo]

So I checked the latest nuget packages for Fody. 1.29.4 en 1.30.0-beta01 are coming with Mono.Cecil.dll version 0.9.6.0; so this is the problem (according to Mono.Cecil).

However, in https://github.com/Fody/Fody/tree/master/Lib/Cecil I see the that the version is 0.10.0 ...

Is it possible to create a new update for fody packaging this latest version? @SimonCropp ?

[hrach]

Any idea for workaround in Visual Studio on Windows?

[bbkillen]

I fixed this in VS4M in the preferences…

…

On Apr 11, 2017, at 2:49 PM, Jan Škrášek ***@***.***> wrote: Any idea for workaround in Visual Studio on Windows? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#302 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATWKVOslmnmOIaNAQFT73QDkFujLHF1xks5ru9k1gaJpZM4M37HA>.

[Lenndev]

Pointing to each other doesn't help... what does help is the "work around" @kanvuduc mentioned. In VS > preferences > .NET runtimes > set Mono 4.8.0 as default

[hrach]

Well, on Windows, there is not such configuration, is there a mono somewhere?

@Lenndev nobody is "pointing", people just try to find the cause and get it logged into a proper issue tracker.

[stefandevo]

Fixing it for now is ok, but for example on VSforMac or XS this means you cannot use c# 7 in combination with Fody with doesn't make me happy...

[galvesribeiro]

+1 with the same issue... Sad to hear we can't use C#7 + Fody :(

[dansiegel]

It seems like this is causing major havoc for a lot of dev's... so glad it's not just me. It seems that the root of this is Cecil, however it is also a Fody problem due to the way in which Fody ships with no dependencies by including Cecil as part of the package. Supposedly the issue should be fixed in 0.10-beta5, however Fody would need to release an updated package with the new Cecil binaries.

[Redth]

This is going to break any Xamarin dev using Fody very soon. It looks unfortunately like this project is a bit dead. I took a quick look at merging in the upstream Cecil changes back into Fody's fork, and it looks like maybe Cecil now includes the functionality Fody had added to their fork, so perhaps it's possible to use Cecil as a true dependency. I may have an extended look at this over the next few days.

[Bartmax]

This is going to break any Xamarin dev using Fody very soon.

Yup, add one more to the list.
My code is full of C# 7 so no workaround for me... 😢

[renzska]

Sadly, like @kanvuduc mentioned, this breaks the usage of Realm. We were about to start using it in a new app, but now we have to find something else. Any recommendations besides sqllite?

[galvesribeiro]

@renzska same case here... Thats why libraries should avoid at all cost to don't take dependencies on 3rd party libraries... It will break Realm all over...

[stefandevo]

Fody/PropertyChanged#226

[SimonCropp]

Can u try fody 2.0

[dansiegel]

@SimonCropp testing this with PropertyChanged in VS for Mac everything looks like it's working right again. Thanks for getting the update out!

[SimonCropp]

Good to hear

[ismly]

@kanvuduc how can I download 4.8.0 for mac?

[tuyen-vuduc]

@ismly Here you are http://www.mono-project.com/docs/about-mono/releases/4.8.0/