Hi Jamie, Each trampoline type has a theoretical maximum, so it is possible to calculate it upfront. Unfortunately increasing the number of available trampolines increases the app's memory usage, and since the theoretical maximum is *way* above the maximum you'll actually end up using, we've set a default value that works fine for most apps.
The number of trampolines used does not change if you run the same code twice - but different code paths will (if you test your app extensively you should catch this though). So, with proper testing you'll be fine. Rolf On Fri, Feb 10, 2012 at 10:23 AM, jamier1978 <[email protected]> wrote: > Hi, > > We have ran in to the "ran out of trampolines of type 2" issue which we have > fixed by increasing the number of trampolines in the additional mtouch > arguments. > > I was wondering if anyone could give me some more information on the > consequences of doing this? > > Does this increase the memory foot print of your MT app or affect > performance? Also, can the number of trampolines required be determined at > compile time (e.g. based on the number of types or methods etc..) or could > the number keep going up the longer your App is running? > > I suppose I'm trying to find out if we increase trampolines to a particular > number and we see no issue during testing can we be confident that we have > enough? > > Thanks for any extra info on this > > Jamie > > -- > View this message in context: > http://monotouch.2284126.n4.nabble.com/Increasing-the-number-of-trampolines-tp4375692p4375692.html > Sent from the MonoTouch mailing list archive at Nabble.com. > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
