I am testing my application on a number of machines. It is fine on every machine except 1.
I'm having problems with one XP machine where in internet explorer, chrome and firefox the Silverlight plugin crashes on EVERY page with Silverlight.
Pages that used to work fine with silverlight 3 crash instantly - including my app and the Silverlight Beta 4 demo page!!! The browser crashes instantly and doesn't even attempt to load the page.
I don't know how to debug this because there's no error. It just crashes instantly in all these browsers.
Reinistalling, rebooting didn't fix the problem.
I'm not sure what it might be, but you could try debug it this way.
Attach to running instance of Firefox with Visual Studio.
Go to menu Debug -> Exceptions... and check all "Break when exception is" boxes.
Now open page that crashes the browser.
Ideally you should catch an exception with debugger. I've spotted this way OutOfMemoryException in my app. Browsers were crashing with no reason, but debugger showed the right direction...
Fixed in RC/RTM (at least for me!)
Related
I have a hobby website:
http://www.chartmygolf.com/Programs/Program.aspx
and for the first time (in six years) someone has said the circle/percentage thing that appears when the program is loading is not appearing, and consequently the program does not load. What could be causing this?
He has installed Silverlight 5.
He is in the USA so I have a bit of time to prepare some ideas. The things I have thought of so far are:
A 32/64 bit mismatch between Internet Explorer and Silverlight versions. If it is this how do I check what 32bbit or 64bit versions they have of each?
Whether they have Silverlight not Enabled in Internet Explorer. (I think this might be low odds because he tried to load it on firefox and chrome with the exactly the same problem).
Does anyone know another Silverlight website page which requires program loading, so I can check if the problem he is having is specific to my page or to Silverlight programs in general?
Jon
EDIT:
Some more info.
He is operating on Windows 7.
He went to the sample Silverlight page (Silverlight SDK Sample Browser) and it loaded most of the way. What doesn't load is the top section and the sidebar which both have spinning circles around them with 100% in the middle.
He is using IE11.
In the add-on section the Silverlight is enabled for both 32-bit and 64-bit versions.
I hope this can be resolved.
I have noticed that after awhile of debug/tweakcode/debug etc that eventually Silverlight starts to crash all of my browsers (i.e. doesn't matter which i fire, they all just crash). If i then go to a site that has Silverlight, it works fine? so it has something to do with debugger + Silverlight not getting along?
I then reboot and the problem goes away? Is anyone else experiencing this kind of weird behaviour?
I have noticed though that if i put breakpoints on the code they all seem to halt, in that it appears that it can instantiate the said .xap etc ok, but just can't seem to render it to screen without a crash?
(There's nothing in the log files and i've tried to attach a seperate VS2008 instance to both IE, Devenv and Blend etc trying to see if i can catch what's causing this to occur?)
There are couple of ways to figure out cause of this issue
One is using XPERF - If you are using Windows VISTA here and here
or using Windbg by getting a memory dump and here is a tutorial from Tess
I'm working with a Silverlight 3 app and using Chrome as my test browser. While debugging I keep getting the popup message:
Plug-in Unresponsive
The following plug-in is unresponsive:
Unknown Would you like to stop i?
Yes/No
How can I turn this off in Chrome? Can VS be set to shut it off only when debugging? It's a real pain when debugging.
Thanks,
Add --disable-hang-monitor to chrome shortcut
Nick - are you using Chrome early builds on the Mac? There are some known issues with Chrome/Silverlight that we are working through with the teams -- most scenarios work though. Is this something you can share so others may verify?
To be honest, I set IE9 as my default browser when debugging Silverlight and switch back to Chrome afterwards. Chrome doesn't seem to communicate to Visual Studio (or vice versa) so I can't get breakpoint and exception information when using Chrome.
We have a large winforms program. On one computer if you are running the program and open IE8 the winforms program freezes and doesn't come back. But if you already have IE8 running when you start the winforms program everything appears to be fine.
The same thing happens regardless of how you start IE8 (normal, no addins, or 64 bit).
My dev box has the same os, motherboard, processor, and memory and it runs fine.
This is on Vista Enterprise x64 Q9550 with 8GB ram.
It runs fine with Firefox 3. The weird thing is there are no web browser controls in the app or anything that should make it related to IE.
I would first start by trying to open a different browner (i.e. Chrome) to see what happens there. My guess is that will work but at least its another point of reference for solving the problem.
Wasn't really browser related. Some of the controls were created on a worker thread so they had no access to the Windows message pump.
Does anyone know how to debug a Silverlight 2 app running in Google Chrome from Visual Studio? Even after making sure that Chrome is the debugging browser, breakpoints are still not being hit.
Have you tried attaching to Chrome manually? Tools > Attach to process?
Chrome isn't officially supported but there are hacks.
Here for example. Halo's comment may give you some help too.
You can have more than one browser running on your localhost.
1) Hit F5 to run debug. Probably opens IE or whatever your default is. F5 your way through the breakpoints until it's loaded. Leave this IE open.
2) Open your other browser, coping the localhost Url into the new browser and run it. New browser should hit the breakpoints.
This works with all browsers, and even emulators like BlackBerry emulators.
Attach to the process manually (Tools > Attach to process), but make sure to attach to the chrome process that lists its type as "Silverlight, ...". Its title should be blank.
If you see your application name in the title, it's because chrome has a separate process for the HTML form that your Silverlight app is in, and the html's title probably matches. Attaching to this process does not load the Silverlight assemblies.
I usually will start debugging the app in IE to make sure that the most recent changes are compiled and running, then launch chrome, clear its cache ('cause it likes to hang onto Silverlight data), paste in the url from IE, and then stop IE and attach to chrome. Extra steps, but worth not spending 3 hours to figure out you are looking at cached assemblies.
This is an issue with Visual Studio interacting with Chrome: http://code.google.com/p/chromium/issues/detail?id=45560. My guess is you need to wait for a Visual Studio patch, but I honestly wouldn't hold your breath. The majority of Silverlight developers just use IE or FF for debugging. (Apparently even FF has some issues now that they've sandboxed their plugins: http://timheuer.com/blog/archive/2010/08/16/enable-silverlight-debugging-in-firefox-visual-studio.aspx#20476). As much as I hate IE, it's really your best bet for debugging Silverlight apps.
Simply set SL app as startup prtoject instead of asp.net and press F5