Bug 14467 - In 6.4.4.12 BinaryFormatter.Deserialize within OnDeserialization throws a System.NullReferenceException when deseralizing a System.Collections.Hashtable but does not happen in 6.4.3.0
Summary: In 6.4.4.12 BinaryFormatter.Deserialize within OnDeserialization throws a Sys...
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 6.4.4
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-09-05 20:52 UTC by Eric Hosick
Modified: 2013-09-16 13:22 UTC (History)
3 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 FIXED

Description Eric Hosick 2013-09-05 20:52:36 UTC
I've been using BinaryFormatter.Deserialize in a project for quite some time.

Today, after updating from 6.4.3.0 to 6.4.4.12 I started getting System.NullReferenceException when using the BinaryFormatter.Deserialize to deseralize a HashTable. I've had to roll back to 6.4.3.0.
Comment 1 Sebastien Pouliot 2013-09-06 08:15:50 UTC
We might have inherited a recent mono bug while updated the BCL. Sadly it means that case was not covered by some unit tests (or used in our test applications).

Can you attach a small test case (unit test or a small app) that shows the issue. We'll fix this and ensure it gets part of the test suite. Thanks!
Comment 2 Sebastien Pouliot 2013-09-08 12:23:59 UTC
Also do you remember if the NRE occured:

* only occured on the simulator ?

or

* did the same happen on devices ?
Comment 3 Eric Hosick 2013-09-08 14:06:07 UTC
It was in the simulator.
Comment 4 Sebastien Pouliot 2013-09-09 10:11:45 UTC
If it works in release (not debug) build for the simulator (or on devices, debug or release) then it's likely a duplicate of bug #14493

Can you try this ? or supply a test case so we can validate this ?
Comment 5 Eric Hosick 2013-09-11 15:14:08 UTC
We will try to provide a test case. We are working hard to meet a deadline for a demo and are currently using Version 6.4.3.0 of Xamarin.
Comment 6 Sebastien Pouliot 2013-09-11 15:35:32 UTC
I understand, no rush. When you have the time try first 6.4.5 which has a fix (the single fix for that release) for a very similar problem (bug #14552).

Setting back to NEEDINFO (which means we, Xamarin, are waiting on more information on the bug).
Comment 7 Eric Hosick 2013-09-16 13:22:03 UTC
I installed 6.4.5 and the issue went away. Thank you.