c# - Visual Studio 2010 hangs on trace point -

c# - Visual Studio 2010 hangs on trace point -

the problem:

whenever seek break or set trace-point in debugger, our application , visual studio freezes completely. after detaching debugger application continues.

this problem related wpf. have migrated our winform application wpf. since problem occurs. im not able find specific part of code wich causes problem. have rolled hundreds of commits without success.

it might related ui thread. if breakpoint set somewhere away ui logic application not freeze or not freeze somwhere in ui thread.

[edit:] utilize windows 7. 64bit visual studio 2010

[update:]

when visual studio hangs, , seek detach before breakpoint displayed, message "unable detach 1 or more processes. outstanding func-evals have not completed". have disabled func evaluation in debugging options. think problem caused func_evaluation can not finish or runs timeout.

is there way see on func_evaluation visual studio hanging?

example:

class someuiviewpresenterexample { private timer m_timer; public void init() { m_timer = new timer(); m_timer.elapsed += elapsedfoo(); m_timer.autoreset = false; m_timer.interval = 200; } private void elapsedfoo(object sender, elapsedeventargs elapsedeventargs) { // there no code within method // on next line trace point "---> elapsedfoo called" freeze debugger }

what have tried: (without success)

enable / disable host process tried debug x86 , x64 processes launched visual studio /safemode ngen update disabled "property evaluation , other implicit function calls" in debugging options disabled symbol servers disabled symbol loading deleted wpf font cache marked several ui elements 'debuggerdisplay("some text without expression")'

(ticket microsoft connect)

probably related problem:

because our application uses .net remoting communicate process, problem similar here. have placed registrations remoted events in own task, without success.

debugger output debugged visual studio:

i have attached debugger visual studio , have observed exceptions,(80010005)

but have no thought wheter relevant problem or not:

(18d8.1708): c++ eh exception - code e06d7363 (first chance) (18d8.1708): c++ eh exception - code e06d7363 (first chance) ..... // snip (18d8.18dc): **unknown exception - code 80010005 (first chance) ..... // 20 seconds freeze until breakpoint nail in ide (18d8.18dc): unknown exception - code 80010005 (first chance) (18d8.18dc): c++ eh exception - code e06d7363 (first chance) modload: 365f0000 36665000 c:\program files (x86)\microsoft visual studio 10.0\common7\packages\debugger\mcee.dll // after go on execution debugger , debugged process freezes forever (18d8.18dc): unknown exception - code 80010005 (first chance) modload: 00000000`02b90000 00000000`02c1c000 c:\windows\syswow64\uiautomationcore.dll (18d8.1a8c): clr exception - code e0434352 (first chance) (18d8.1a8c): clr exception - code e0434352 (first chance) (18d8.1a8c): clr exception - code e0434352 (first chance) (18d8.1a8c): clr exception - code e0434352 (first chance) (18d8.1a8c): clr exception - code e0434352 (first chance) (18d8.1a8c): clr exception - code e0434352 (first chance) (18d8.1a8c): clr exception - code e0434352 (first chance) (18d8.1a8c): clr exception - code e0434352 (first chance)

thank ideas or hints

manuel

the more @ this, more suspect it's because you're not using wpf timer. if seek utilize regular timer class rather wpf dispatcher timer, run risk of trying update ui on non-ui thread - potentially cause of problem (since datacontext part of ui technically).

more info here:

dispatchertimer vs regular timer in wpf app task scheduler

c# wpf visual-studio debugging