After Save -> close page crash
7 Replies
Hi Adrian Crutchfield,
Sorry for the inconvenience caused.
We have analyzed your query and we are unable to reproduce the reported issue “Cannot access a disposed object”, but given your stack trace we have made some tests and we were able to reproduce an exception closer to your stack trace and it is the “UIThreadAccess exception” while disposing the image editor in saved event.
Please refer below screen shot for stack trace details.
Screen shot:
Having said that both these exception is because of the UI thread, which is running while saving and at the same time the Image Editor is disposed. This can be handled in sample level by invoking the main thread to dispose or remove editor in your application. Since we are not aware of the exact scenario where you are removing the editor in your application we have prepared a simple sample to overcome this issue by removing the editor on invoking the main thread, you can download the sample from the below link.
Sample Link: https://www.syncfusion.com/downloads/support/forum/136702/ze/ImageEditor_MSBuild2018-1080724060.zip
Code snippet:
editor.ImageSaved += (object sender, ImageSavedEventArgs args) => {
Device.BeginInvokeOnMainThread(async () =>
{
mainGrid.Children.Remove(editor);
});
};
Note: We have already fixed “Cannot access a disposed object” exception in for android in the assembly version 16.1.0.37. We have not come across “Cannot access a disposed object” in iOS, so if you could provide your exact scenario it would be helpful for us to fix and provide you a better solution.
Device.BeginInvokeOnMainThread(async () =>
{
mainGrid.Children.Remove(editor);
});
};
Note: We have already fixed “Cannot access a disposed object” exception in for android in the assembly version 16.1.0.37. We have not come across “Cannot access a disposed object” in iOS, so if you could provide your exact scenario it would be helpful for us to fix and provide you a better solution.
Let us know if the above sample solution helps.
Regards,
Jeya k
Jeya k
Hi Adrian Crutchfield,Sorry for the inconvenience caused.We have analyzed your query and we are unable to reproduce the reported issue “Cannot access a disposed object”, but given your stack trace we have made some tests and we were able to reproduce an exception closer to your stack trace and it is the “UIThreadAccess exception” while disposing the image editor in saved event.Please refer below screen shot for stack trace details.Screen shot:Having said that both these exception is because of the UI thread, which is running while saving and at the same time the Image Editor is disposed. This can be handled in sample level by invoking the main thread to dispose or remove editor in your application. Since we are not aware of the exact scenario where you are removing the editor in your application we have prepared a simple sample to overcome this issue by removing the editor on invoking the main thread, you can download the sample from the below link.Sample Link: http://www.syncfusion.com/downloads/support/forum/136702/ze/ImageEditor_MSBuild2018-1080724060.zipCode snippet:editor.ImageSaved += (object sender, ImageSavedEventArgs args) => {
Device.BeginInvokeOnMainThread(async () =>
{
mainGrid.Children.Remove(editor);
});
};
Note: We have already fixed “Cannot access a disposed object” exception in for android in the assembly version 16.1.0.37. We have not come across “Cannot access a disposed object” in iOS, so if you could provide your exact scenario it would be helpful for us to fix and provide you a better solution.Let us know if the above sample solution helps.Regards,
Jeya k
Thank Jeya,
This does solved the problem.
CT
SIGN IN To post a reply.
