I have following problem: Sometimes, when I debug a C++ project in VS 2013, my complete Windows freezes! This means:
GUI is updated (i.e. previous opened Task Manager is updating values)
Can not close VisualStudio
Can not close any program (i.e. firefox, the program which is been debugged, outlook, ...)
killing any process via Task Manager not working
Klicking Windows start button not working
Hitting Strg+Alt+Del not working
The only thing I can do is press and holding the I/O Hardware button at my Laptop
The system is a Windows 7 Enterprise x64 with SSD, 16GB RAM and i7 CPU. Symantec Endpoint Protection is installed from our IT. Some of my collegues have the same problem. We think, that this problem only occures if mixed-Debugging with Managed-Code, Unmanged-Code and COM in code is used.
Thanks for your Help!
Related
I'm trying to run appcelerator studio in my Desktop.
AMD Athlon II x4 640 3.00 GHz
Ram 4gb
64bit win 8.1
120Gb SSD Samsung 840 EVO
so, in my laptop i7 8gb ram etc.. run smoothly.
When I'm trying to start the studio doesn't respond, not even in task manager.
I'm using CLI and work fine..
I can't find any log file. Which appc studio keep in workspace which one I have no create yet because I can't open the studio.
I run the command appc platform to start the studio from the CMD but nothing happens and this message appears:
{"success":false,"description":"platform command usage: appcelerator platform <api> <method/arguments>"}
I uninstalled AVAST and check first the blocked programs, but nothing..
I disabled Windows firewall too.
Reinstalled the studio many times using different versions of node. But nothing.
And of course I tried to come in contact with the appc team but I can't....
I'm thinking about 4Gb ram limitation; if that blocks the program from starting.
I also try to open the program logged in and logout from CLI.
Any idea? any one with the same problem?
I am not stuck in loading screen the studio try to verify my account and communicate with server.
Studio just won't start at all.
I'm sorry for my bad English.
sorry for your issue.
First - I am assuming your running Windows (Linux is no longer supported)
The CLI command your using appc platform does not launch studio. That is used for accessing platform APIs and thus requires you to provide an API to use.
To launch studio from the CMD line on Windows you would need to cd into your Appcelerator Studio directory and run the associated program. When installing studio, we do put an icon on the desktop, which is by far the easiest way to start it up.
Your right about your RAM limitation. While you'll find that studio does "run" it will be extremely slow, especially once you start using the Android / Windows emulators etc. Windows takes up 1-2GB of Ram on its own, leaving very little for any development tools.
Our recommended configuration for Windows machines is:
* Windows 8.1 or higher
* 16GB of RAM
I would also think about a faster proc as well.
We are in the process of updating our documentation on the pre-reqs' as its a bit misleading. While we say 4GB of RAM is suitable, what we are talking about is 4GB of 'free memory' on top of everything else you have running, not 4GB of total system memory.
I am not able to start any of the Mobile Emulators for Windows Phone 10 (version 10.0.10240).
When I start it from the VS 2015, it gets stuck at "OS is starting". In the Hyper-V Manager, I can see the status "Starting (10%)" for the whole time. After some time, the machine is automatically restarted and it gets stuck at "Starting (10%)" again. Then it timeouts again and the emulator shows an error: "The virtual machine cannot be started because the file rdvgm.exe that is required to start the RemoteFX Manager process does not exist". That is weird, because I do have the rdvgm.exe in the C:\Windows\System32.
I have seen that there are some questions with the same error, but they are resolved by fixing the network switch or by killing devenv.exe after it shows "OS is starting". I have tried both, but it did not help. The network switch issue is different (I have seen it on a different computer - in that case the emulator starts correctly, but VS is not able to connect to it). I am stuck at "Starting (10%)".
What can I try to get it working? Windows Phone 8 emulator is working without any issue.
Thanks
The problem was that Hyper-V detected a graphic card which is able to work with RemoteFX (integrated Intel GPU) but the dedicated one (AMD Radeon) was not supported. I was not able to convince Hyper-V to ignore the dedicated one. When I disabled the RemoteFX support for Hyper-V (unchecked it in the Intel GPU setting in the Hyper-V configuration), it started working.
I found this Microsoft technical support desk yesterday. Its an on line chat with their technical people. I don't know if it covers all MS products. I was asking them about Outlook. Could be worth a try. I found it a touch slow at times, but ...
https://www.awasa.microsoft.com/en-GB/consultation/index?id=914801398064643&skuId=0
Hyper-V has problems enabling RemoteFX with some dual gpu graphics cards. Disabling one of the graphics cards in device manager solved the problem for me:
Disable one of the integrated graphics cards in device manager. I disabled Intel (R) HD Graphics 4600 and left NVIDIA GeForce GT 740M enabled.
Reboot Windows.
Delete the existing mobile phone virtual machines in Hyper-V Manager.
Start Visual Studio and deploy your app again.
I'll be honest, with much distress, I performed a complete factory reset. Reinstalled only Visual Studio 2015 Community edition (only with the tools I needed and not any other emulators such as Android), and it worked after setting up Hyper V as instructed via documentation on dev.windows.com
Visual Studio 2013 for Desktop is displaying incorrectly. When I open the program, it displays correctly but upon moving my cursor over links or images inside of the interface, they either expand to fill the whole window or the line itself blurs.
I'm running Windows 8.1. I've run it in compatibility mode for XP, Vista, and 7. I've run as administrator. I've reinstalled and repaired. This error is easily reproducible and has occurred over the course of 3 days.
Any help would be appreciated.
Can only guess that your video card vendor happens to maintain a bad driver (or Windows Update pushed a bad version to your machine).
http://support.microsoft.com/kb/2894215
The workaround is to disable hardware graphics acceleration and test again.
Today i tryed to install wp8 sdk and it installed successfully. but when i'm trying to open visual studio my pc going crash and restart every time. I think its mainboard v-hiper problem or something else. my pc informations
Packard Bell TJ75
CPU : I5 430M
Ram : 3 GB
Graphics : HD 5650 1 GB
BIOS : Phoenix Tec. LTD
how can i fix that problem ?
-Thanks,
Sorry for my english.
What is the crash? A bluescreen? And what codes? Does system event log say anything interesting?
I don't think Visual Studio will try to start the phone emulator until you actually try to debug a phone project in it, so I don't see the immediate connection to Hyper-V.
Does your system crash when you open Visual Studio with no active project? That might absolve Hyper-V.
Alternatively, can you create some other virtual machine image (e.g, from Ubuntu or another Windows), and try booting that one? If your host machine crashes when you do that, then it would implicate Hyper-V.
Windows can crash if it gets too tight on system RAM, and 3G of RAM is not very generous. Both Visual Studio and Hyper-V use a lot of RAM, so you might indeed have problems running them both at the same time.
When running the debugger about 50% of the time, Visual Studio 2010 freezes and also locks up my entire machine. I can't even get to Task Manager. Nothing works except my mouse will still move. The only way to recover is to hard boot the machine which takes about 15 minutes each time. I don't have anything else running on my machine at the time except VS, IE 8 (sometimes) and Outlook.
I am running Windows XP on a Lenovo T400 with 3G RAM
Has anyone seen this behavior? If so, how did you fix it?
Thanks,
Rhonda
You don't mention what language your app is but I have run into this with our C++/CLI application on occasion. To avoid it, I changed the Project properties / Debugger and specify "Native" or "Managed" explicitly for the debugger type. The default of "Auto" can get confused.
Also, if you use Application Verifier from Microsoft, I have had VS hang while AV was configured to verify our .exe. To avoid this, we have to launch the app under the debugger as "Native".