Hi,
The new crash prevention feature isn't compatible with the XamWebHtmlViewer.
- Go to your samples for 9.2: http://labs.infragistics.com/silverlight/lobsamples/2009.2/
- Go to the html viewer sample
- Click on the "navigation and custom html" sample
- Click on the "launch" button
- BLAM! plugin crash
I tried another HTML viewer component and it's the same.
It seems that there's a System.AccessViolationException being raised when the control listens for a DOM event and raises it again on the Silverlight side (the DocumentLoaded event for your component and the SizeChanged for another one I tested).
Hello,
I've just tested your scenario on two different computers (samples 9.2 and Firefox 3.6.6) and there weren't any problems or exceptions. It seems to me that there is a problem with your Firefox.
Regards,
Doychin Dochev
I ran around the office and tried the samples again.
Result: they always crash with the SL 4.0 runtime but they run fine with the old SL 3.0 runtime.
My current crashing version of Silverlight is 4.0.50524.0 (the developer edition). My colleagues with the regular version experience the crash as well.
Can you confirm with me that you tried the samples with the latest SL runtime?
I ran a few more tests and realised that the plugin didn't crash if there are no tabs open.
If I open the test samples on a new tab it crashes.
My Silverlight plugin is: 4.0.50524.0
I tested 9.2 and 10.2 samples (I opened them in a new tab as you described) and there weren't any exception.
I'm not sure how to simulate your problem.
I created a case for our developer support team.They will contact you ASAP and will try to identify the issue.
Thanks,George
Could you move the bug report to the account I'm writing under? I used my developer account to report the bug and my boss has the account with the support subscription.
I only realised my mistake today.
Cheers.
I've just noticed that going to the current HtmlViewer sample with Chrome and resizing the window makes it crash as well.
I guess the implementation of the HTML viewer is very browser-dependant.
Can I hope to get a fix for that? It's been quite a while since I reported the issue and I don't see any progress on a solution.