Search

VS2012 Code Window scrolling garbles text by Dwaine Wright

Closed
as Not Reproducible Help for as Not Reproducible

2
0
Sign in
to vote
Type: Bug
ID: 778870
Opened: 2/8/2013 4:59:52 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
HELP! The VS2012 code window is driving me crazy. using the mouse wheel, arrow keys, scroll bar, etc. garbles the text. Describing the garbling is not trivial. It's almost as if the majority of the text on the window gets locked in place, but a small portion of the top and bottom of the code window does show scrolling text in the back ground. This issue seems universal on my new laptop. All code windows, from old 2010 projects, as well as brand new projects do the same thing.

Very similar to another thread for VS2010. I have followed all suggested steps, by Lucy-Liu, in that thread except the last.

http://social.msdn.microsoft.com/Forums/en-US/vseditor/thread/449f9307-afd1-4387-afdb-64cf3256dead

Step 4 (reset settings) actually fixed it for about 15 minutes, but then the phenom returned.

Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

open a code window and scroll

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

English

Actual results

garbled text windows while scrolling.

Expected results

clean scrolling and consistent text appearance.
File Attachments
File Name Submitted By Submitted On File Size  
VS2012_2-8-2013 4-59-06 PM.mp4 2/8/2013 3.82 MB
Sign in to post a comment.
Posted by Microsoft on 3/8/2013 at 4:26 PM
We're glad the issue was cleared up.

Thanks,
Language Experience Team
Posted by Dwaine Wright on 3/1/2013 at 5:07 PM
Don't know why MS would not be interested in this very serious usability issue. Turns out I figured it out. Our IT department uses RAdmin as a support tool. This SW uses a "Mirror driver" that apparently wreks havoc with Windows 7 Aero, etc. Disabling this "RAdmin Mirror Driver V3" and rebooting cleared it up.
Posted by Microsoft on 3/1/2013 at 7:51 AM
It's been a while since our last communication so we're going to resolve and close this issue. If you're still experiencing problems, please reactivate or create a new Connect bug.
 
Thanks,
Ala Shiban
Language Experience Team
Posted by Microsoft on 2/21/2013 at 3:10 PM
Hey Dwaine, thanks for your patience. We haven't been able to reproduce the problem internally. We suspect that the issue is graphics-card related. Have you tried updating your graphics drivers?

Can you let us know:
What GPU does the laptop have?
Does the problem occur even with all the extensions turned off?

The more details you can provide, the higher the chances we have of reproducing and tracking the issue.

Thank you,
Language Experience Team
Posted by Dwaine Wright on 2/15/2013 at 1:25 PM
I would really appreciate an idea of when this may be addressed. My brand new development laptop is all built and ready to go. I can do anything I want on it now.... except development.

I may use an MSDN case for this if I don't hear back soon.
Posted by Dwaine Wright on 2/12/2013 at 2:52 PM
Thanks! Triage.... sounds serious.

I've verified that this issue appears in both VS2012 AND 2010, but NOT 2008 (don't have 2005 installed). The 2008 and 2010 editions are only BIDS, but the result is the same. VS is essentially unusable.

This is Win 7 Enterprise, 64 bit.
Posted by Microsoft on 2/10/2013 at 6:54 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Dwaine Wright on 2/9/2013 at 4:48 PM
btw,

This is a fairly new installation of VS2012 on a new Lenovo W530. This issue happens both on LCD and external monitors and thus on both the integrated and discrete GPUs.
Posted by Microsoft on 2/8/2013 at 5:50 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.