Menu
Ok, on the edge of frustration here... and I am having the worst time of my life. For the life of me, I cannot solve this issue with my Visual Studio 2013 installation. No matter what I've tried, it continues to throw up "Invalid Pointer" every time I attempt to preview my solution in a browser.
Before I had other issues, but I uninstalled and re-installed. Updated, rebuild solution/project, set the browser to bypass the proxy for localhost, loaded the latest version of IIS and Asp.Net... you name it. And it just continues to greet me with the following:
It's not telling me anything else. I did have VS 2012 and VS 2010 on this machine, but I uninstalled them. Now I'm left with this. What is the deal with this occurring? Can anyone provide some insight? I have two hard drives on this machine. If this doesn't work, I'll try to install it on the other side and hope it works well with SQL Server, because SQL is on my C drive. I have a dual boot and will just boot into the other Windows 8.1 Pro side and try that. Figured I find a solution here first and learn a thing or two before resorting to that. Thanks!
650
"Invalid pointer operation" means you freed memory that didn't belong to you. One of these three things is the cause: Your program freed something that had already been freed once before. Your program freed something that was never allocated in the first place.
An invalid pointer reference occurs when a pointer's value is referenced even though the pointer doesn't point to a valid block. One way to create this error is to say p=q;, when q is uninitialized. The pointer p will then become uninitialized as well, and any reference to *p is an invalid pointer reference.
I had the same problem. I had updated visual studio (update 4) but my connection failed during the update so I didn't update visual studio completely. And the error "Invalid Pointer" occurred each time I was debugging my program, Until I update it once more but this time completely. So no more error.
I suggest you to update your visual studio and here's where you should update it : http://www.microsoft.com/en-us/download/details.aspx?id=44921
166
I think this problem is caused by importing VS2010 settings. Anyway, this solved the problem for me:
\Users\<Username>\AppData\Roaming\Microsoft\VisualStudio\12.0
\Users\<Username>\AppData\Local\Microsoft\VisualStudio\12.0
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0
_12.0
22
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
