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
Related
I have written an application in WPF/VB.net and have been testing it on a few different computers.
I have never experienced this issue on my development machine but one of my test machines has a strange issue where combo box lists and context menus are invisible.
The objects are there and you can select items from them but they are not being drawn.
I am scratching my head with this and have been searching for evidence of similar issues online but not really found anything.
I would like to completely rule out that this is a programming issue before going down the route of pointing the blame at any particular hardware my company is using.
I am using one click deployment and have transparency enabled on my windows.
This is an intermittent problem and restarting the PC will fix the issue. Restarting the application does not make the issue go away.
Thanks
Check that the machine you have problems with has the correct .net framework loaded. If you are using any other products such as Silverlight then check versions.
This issue was fixed by forcing software rendering on windows XP within the App.
This was done by adding the following line to application start up.
RenderOptions.ProcessRenderMode = System.Windows.Interop.RenderMode.SoftwareOnly
I'm developing a SL4 OOB application that has suddenly started giving me the white screen of death.
If I try to run it 'in-browser' and check the console I can see the error 2105 : 'Failed to load pre-requisites for the application' but there's very little info about it anywhere.
None of my breakpoints get hit. Even starting the app with F11 (step into) doesn't get me anywhere.
I can run other Silverlight projects just fine so it's not the runtime. I've even copied the source into another project to see if that might help but to no avail.
Does anyone have any ideas how I might get started fixing this?
I have seen this myself and it was a pain..
What I had to do was a system restore, de-installed all traces of Silverlight and Blend and then reinstalled them all. However I had also just installed Silverlight 5 RC which didn't play nicely with Telerik and might have been the problem.
There is also some information about this error here:
http://connect.microsoft.com/VisualStudio/feedback/details/530074/unhandled-error-in-silverlight-application-2105-when-building-as-an-x86-configuration.
Is this your problem?
Damn it, I hate answering my own questions but the problem was quite obscure.
Somehow, I managed to get a regular .Net reference in my Silverlight project through a Nuget package. That was it.
DOH!
I have a strange behavior in VS2008 a few times: After some changes in a xaml file, removing a control with a compile time error, VS2008 keeps saying the error is still there, even when the control itself is not there anymore. I could only fix it by creating a new xaml file, copying the content and deleting the original file. I cleaned the solution, rebuild, restarted VS, restarted the computer and nothing exorcise this ghost error. The solution builds and runs successfully, but I can't see the design time editor.
Does anyone have faced this strange behavior before?
It would be really nice if I could find an easier way to workaround/avoid it.
I'm sure this is not the answer you want, but you'll experience much greater WPF development performance if you can upgrade to VS2010. VS has improved so much it's almost listless. Plus if you try to run your app with 2010 and still have the same issue, there's another whole group of devs who could try to reproduce the error.
I'm using Windows 7 Professional (x64) and having installed .NET 4.0 RTM on my machine.
Since 2 days I'm noticing that every WPF application that I'm trying to run hangs and becomes non responsive (a not responding text is appended to it's title bar) and it's painted white.
There is no info regarding any exception, no error message. Nothing. Even the Event Log shows that there was "application hang" event (code 1002) and nothing more.
This problem is for everything that is written in WPF, even for products like NHibernate Profiler and other stuff that I was using on a regular basis without any issues.
Tried to reinstall .NET 4.0 and nothing changed. Any ideas why this might be happening?
I had the same problem. It was a corrupt font cache!!
See http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/7cc032c1-5f4d-4518-adc6-f53afd051e6b for a solution.
If I had to guess I would say video drivers. It might help to try attaching Visual Studio's debugger to the hung process (Debug -> Attach to Process) making sure that Managed Code is the selected debugger type. Then you can break into the debugger and maybe see a common stack trace.
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!)