I used Visual Studio profiling on vs2015, and for a few times it worked great, I could see all allocations, call stack, etc. After a couple of days it stopped working, I could take snapshots but when clicking on one of the entries it only showed "Analyzing heap details..." at the bottom but nothing appeared. I installed vs2017 to check and the same happened! It worked for a few days but now it's stuck again. There must be something wrong that I'm doing, but I don't have any ideas what it could be, anyone had the same issue, and discovered the reasons for this and how to solve it? Thanks!
PS: I'm on the same project when using vs2017, and the compiler is still 2015, I cannot change that at the moment.
​Cool, disabling and re-enabling the heap profiler solves this.
Related
Randomly (and infrequently), Visual Studio (2017) will abruptly refuse to run my C++ project. This will suddenly start happening in the middle of a session.
Visual Studio will still build the project and generate the executable, however, the following cryptic error message appears every time I want to run my program. No changes were made to the configuration or project and it strangely happens after an innocent build.
(It goes without saying but I tried extensively checking for solutions to this problem and no solution worked or was applicable)
Whether I add a new configuration setting or play with the existing settings (Release/Debug, x86/x64), nothing fixes it except performing a full repair (and that takes a very long time). Creating a new project didn't help either, but running it in VS 2015 is successful.
This happens approximately once a week, so I would greatly appreciate knowing how this error can be fixed (or at least avoided).
After some more experience with it, it appears just to be an issue with Visual Studio when builds are too large and executed too often (it happened to multiple computers). More specifically, it could come about as a result of using many templates and applying a large number of explicit template specializations. By building with only the template specializations I need for testing, the issue doesn't come up.
This is usually caused by VS mixing release and debug binaries for me. I have a script which cleans all the output directories, including the garbage VS puts into the projects .vs and Windows Temp folder. This always fixes the issue for me.
I'm using MS Visual C++ 2010 Express. When I want to run a program, it only works the first time. With this I mean that after I run it for the first time, and change my code all together and then try to run it again, it just keeps running my old code. How can I prevent this from happening?
p.s. - I use 'Build Solution' after I'm done with my new code but it still happens
Figure I might as well make it an actual answer:
If you clock is tempered (#anhoppe) then that could cause a problem, and it could also be something to do with your debugging cache. I recommend research in that. One place to look could be this: How to reset the VisualStudio (VS2010, VS2012) debugger cache?
And finally, seemingly obvious, try the "Rebuild Solution" (#Kevin) if you haven't already.
I am using VS2008 for my VC++ coding.
I observe lots of inconsistency (Sometimes intellisense works fine & sometimes it suddenly stops working) wrt intellisense.
And sometimes intellisense stops all of a sudden. And manily for vector in VC++ i see it doesnt work at all.
I am really bugged of VS2008 (I feel VS2005 was simply superb compared to VS2008 user interface). VS 2008 is too bugging.
Can anyone kindly help me in getting rid of this error & make intellisense working fine.
You can delete the .ncb file to force it to rebuild the intellisense you have to close the solution if you want to do this, reopen the solution after deleting, or you can purchase Visual AssistX which is what I use at home and work.
The other thing is that they have rewritten intellisense as of VS2010 so it uses SQL to store the DB and improve the performance.
I know this is not much comfort to you but intellisense is notoriously annoying.
This is probably way too vague for any concrete answers, but this issue has been bothering me so I figured I'd give it a shot here:
Every time I hit F5 to run a project (and I'm talking something tiny 2 - 3 source files), first of all half the time it tells me that I need to rebuild the project even if the only change I made was add a breakpoint and then takes maybe ~20s to actually get the program running. This is a very basic command-line program and with gcc everything happens much, much faster. Any ideas?
PM
When using VS2010 on older operating systems (Like WinXP), then one should make sure to install latest UIA (Windows Automation) component MS KB971513. Failing to do this will cause VS2010 to perform poorly.
Also check ScottGu's Blog for other important hotfixes
The long waiting time before VS actually starts the application when hitting F5 occurs in VS 2008 as well. The simple solution to that is to delete the .suo file. I don't know if VS 2010 uses .suo files, but at least it's something you can try.
This might not be the case, but I remember VS used to act like this when I had lots of breakpoints.
After a Windows update yesterday, I've run into a terrible problem. The debugger suddenly is creating issues.
When I bring up Visual Studio from the start menu, the debugger appears to start, but there is no console window and nothing happens for a long time.
But, if I start it from the VS command prompt, it works, but only once. This is become a nasty issue, and any help/pointers are highly appreciated.
Note: This problem happens with all the C++ projects on my system.
A quick work around would be to start without debugging, ctrl + F5 I believe. If the same thing keeps happening it will be easier to pinpoint what is wrong. Also additional information about what is not working would be helpful.