Stepping into functions when Debugging will crash

[GoogleCodeExporter]

What steps will reproduce the problem?
1. In a debug session
2. Use F11 to step into multiple functions (cross file)
3. Eventually, it will crash just as it steps into a function

What is the expected output? What do you see instead?

- Everything visually looks right, it even shows the expected scroll bar of the 
new file that has the function you just stepped into, VS just crashes without 
any error message or any other information.

What version of the product are you using? On what operating system?

- 0.7.1, Windows 8, VS 2012.  The solution contains a lot of projects (50+) and 
hence a lot of files.  Using the new P4VS (perforce) extension.  Also have 
Visual Assist extension if that matters.

Please provide any additional information below.

- Typically, once you are able to get the crash, it is 100% reproducible (debug 
from the same place and step into the same functions, crashing in the same 
place).

I have verified that removing this extension and repeating the same steps (and 
more) will NOT crash visual studio, so definitely has something to do with this 
extension specifically.

Otherwise, this extension is awesome and can't imagine working without it!  
Thanks!!

Original issue reported on code.google.com by lorenz.b...@gmail.com on 15 May 2013 at 1:58

[GoogleCodeExporter]

I was able to reproduce this and it seems to only happen in VS 2012 (not my 
usual IDE). Most likely this has something to do with VS 2012 opening the files 
it steps into in 1 tab. When it steps into a new file, the previous TextView is 
disposed and Progressive Scroll tries to access the disposed object in its 
render thread.

I should have a fix for this soon.

Original comment by freaksken on 15 May 2013 at 8:28

• Changed state: Accepted

[GoogleCodeExporter]

Should be fixed in 0.7.2

Original comment by freaksken on 15 May 2013 at 11:36

• Changed state: Fixed