Bug 3054 - WCF call System.ServiceModel.ClientBase.InvokeAsync works on simulator but crashes on device
Summary: WCF call System.ServiceModel.ClientBase.InvokeAsync works on simulator but cr...
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 5.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-01-25 03:44 UTC by Curtis Bailey
Modified: 2012-01-25 07:19 UTC (History)
2 users (show)

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

Crash Report (39.13 KB, text/plain)
2012-01-25 03:44 UTC, Curtis Bailey

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:

Description Curtis Bailey 2012-01-25 03:44:59 UTC
Created attachment 1265 [details]
Crash Report

I'm a WCF silverlight proxy to call a WCF service. This works fine on a simulator but crashes on a device. See attached crash report.

OS Version:      iPhone OS 5.0.1 (9A405)
Monotouch: 5.0.4
Mono 2.10.8 (tarball Mon Dec 19 17:43:18 EST 2011)
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-01-25 07:19:15 UTC
This looks like you ran out of a certain type of trampolines.

For more information see this (which also explains how to fix it):

The crash report doesn't say which type of trampoline (0, 1 or 2) you ran out of, but this information is printed to the device console (which you can view using Xcode's Organizer).

Please reopen the bug if increasing the number of trampolines doesn't work.