Bug 35681 - [Mono] 'Destination array was not long enough' in ClientRuntimeChannel.EndProcess
Summary: [Mono] 'Destination array was not long enough' in ClientRuntimeChannel.EndPro...
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Martin Baulig
URL:
Depends on:
Blocks:
 
Reported: 2015-11-09 08:14 UTC by greg.rivington
Modified: 2016-11-11 10:10 UTC (History)
3 users (show)

Tags: BZCU
Is this bug a regression?: ---
Last known good build:


Attachments
Visual Studio 2012 reproduction solution (36.68 KB, application/octet-stream)
2015-11-13 11:30 UTC, greg.rivington
Details


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 NORESPONSE

Description greg.rivington 2015-11-09 08:14:22 UTC
Updated to the latest alpha of Xamarin Android as we require the fix for https://bugzilla.xamarin.com/show_bug.cgi?id=32886

But now, we are getting 'Destination array was not long enough. Check destIndex and length, and the array's lower bounds'.

Stack trace:

   at System.Array.Copy (System.Array sourceArray, Int32 sourceIndex, System.Array destinationArray, Int32 destinationIndex, Int32 length) in /Users/builder/data/lanes/2098/9d7074e1/source/mono/mcs/class/corlib/System/Array.cs:line 961
   at System.Array.Copy (System.Array sourceArray, System.Array destinationArray, Int32 length) in /Users/builder/data/lanes/2098/9d7074e1/source/mono/mcs/class/corlib/System/Array.cs:line 920
   at System.ServiceModel.MonoInternal.ClientRuntimeChannel.EndProcess (System.Reflection.MethodBase method, System.String operationName, System.Object[] parameters, IAsyncResult result) in /Users/builder/data/lanes/2098/9d7074e1/source/mono/mcs/class/System.ServiceModel/System.ServiceModel/ClientRuntimeChannel.cs:line 464
   at System.ServiceModel.ClientBase`1+ChannelBase`1[TChannel,T].EndInvoke (System.String methodName, System.Object[] args, IAsyncResult result) in /Users/builder/data/lanes/2098/9d7074e1/source/mono/mcs/class/System.ServiceModel/System.ServiceModel/ClientBase.cs:line 404
Comment 1 Al Clark [MSFT] 2015-11-10 10:47:01 UTC
I have emailed Greg asking for a sample project  and version information.

Xamarin Studio in Windows
"Help -> About -> Show Details -> Copy Information [button]"

Visual Studio
"Help -> About Microsoft Visual Studio -> Copy Info [button]"

Xamarin Studio in OS X
"Xamarin Studio -> About Xamarin Studio -> Show Details -> Copy Information [button]"
Comment 2 greg.rivington 2015-11-13 11:30:19 UTC
Created attachment 13805 [details]
Visual Studio 2012 reproduction solution

Hi Alan,

I’ve attached a Visual Studio 2012 solution that contains a WCF service project and an Android client project.

If you install the service on a machine and then change the variable name ‘machineNameRunningAndroidService’ to the name of the machine, you should see the issue.

I have left in our new workaround just so you are aware.

The issue was seen on the latest Alpha release that was available through: Visual Studio -> Tools -> Options -> Xamarin -> Android Settings -> Notify me about ‘Alpha’ updates.

But I currently have the latest Stable release as our workaround also means we do not see the following issue anymore (which is the reason our company hasn’t upgraded Xamarin for a while): https://bugzilla.xamarin.com/show_bug.cgi?id=32886 

Hope this helps!
Comment 3 Martin Baulig 2016-11-11 10:10:12 UTC
This has been in NEEDINFO state for the past year, I suppose the problem does not exist anymore?