Crash in AnimatedBasePage when returning from tombstone


This issue has occurred a few times on an actual device right after returning from tombstone. This is on Mango, using WP7Contrib 1.3 and 1.4. Unfortunately I haven't been able to reproduce it with the debugger attached, so I don't have any further contextual information or a proposed fix.
Exception message: "Navigation is only supported to relative URIs that are fragments, or begin with '/', or which contain ';component/'. Parameter name: uri"
Stack trace:
System.Windows.Navigation.NavigationService.Navigate(Uri source)'System.Windows.Controls.Frame.Navigate(Uri source)'
WP7Contrib.View.Controls.Extensions.ApplicationExtensions.Navigate(Application application, Uri uri)'WP7Contrib.View.Transitions.Animation.AnimatedBasePage.<OnTransitionAnimationCompleted>b__4()'
System.Reflection.RuntimeMethodInfo.InternalInvoke(RuntimeMethodInfo rtmi, Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess, StackCrawlMark&#38; stackMark)'System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, StackCrawlMark& stackMark)'
System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)'System.Delegate.DynamicInvokeOne(Object[] args)'
System.MulticastDelegate.DynamicInvokeImpl(Object[] args)'System.Windows.Threading.DispatcherOperation.Invoke()'
System.Windows.Threading.Dispatcher.Dispatch(DispatcherPriority priority)'System.Windows.Threading.Dispatcher.OnInvoke(Object context)'
System.Windows.Hosting.CallbackCookie.Invoke(Object[] args)'System.Windows.RuntimeHost.ManagedHost.InvokeDelegate(IntPtr pHandle, Int32 nParamCount, ScriptParam[] pParams, ScriptParam& pResult)'
From the latest source code (71915, v1.6) I see that in AnimatedBasePage.OnTransitionAnimationCompleted() the try block only contains the call to the dispatcher, but no try/catch is used inside the anonymous function that is passed on to BeginInvoke(), so I assume the issue is not fixed?


oriches wrote Dec 6, 2011 at 10:15 AM

Do you have a test app that reproduces this every time?

ali_futu wrote Dec 16, 2011 at 11:39 AM

Unfortunately I haven't been able to consistently reproduce the issue. I will post a test app or steps to reproduce if and when I can.

wrote Feb 22, 2012 at 6:30 PM

wrote Feb 14, 2013 at 6:15 PM