C++ runtime error pythonw - c++

I have been trying to run a script to generate a mandelbrot image using matplotlib however I am getting a very peculiar error. I am running the script through IDLE, running it for the first time does nothing but running it again after that brings up a window that says:
"Runtime error!
Program: C:\Python27\pythonw.exe
This application has requested the Runtime to terminate it in an unusual way."
The name of the window that pops up is Microsoft Visual C++ Runtime Library
I have previously gotten errors about pythonw when trying to run image related stuff, usually the plot will stop responding and a message displays "pythonw.exe has stopped working".
I have searched high and low for a solution to this and google shows a few people having similar problems but no one replying to their posts.
I have also tried installing microsoft visual x64 C++ 2010 redistributed package but that aborted stating that there was a more up to date version present
interestingly looking through windows update history shows some failed security updates for microsoft visual C++ 2008 that did later install. (don't know if thats relavent)
Running windows 7 64 bit and python 2.7
Was wondering if anyone had any ideas as to what was going on and how to fix it because I sure don't
Thanks in advance!

Related

Merging of ETL files has failed (0x80071069) (Flags: 0x0000001f)

I am trying to profile my application using the built-in profiler in Visual Studio 2017:
However when I close the application, this is what appears:
This is what I see in output window:
Profiling of 'MyProjectName' started.
MyProjectName has exited.
Profiling of 'MyProjectName' stopped.
Diagnostics session stopped with errors.
Merging of ETL files has failed (0x80071069) (Flags: 0x0000001f).
What's wrong? I am running MS Visual Studio Community 2017 on Windows 7 x64. I am profiling C++ Qt application.
I had this issue with that exact same error code 0x80071069. I noticed my WMI Performance Adapter Service (wmiApSrv) was stopped. Starting it back up resolved my issue and I was able to successfully profile my application.
In the past I had seen a similar error caused by my C: drive running low on space due to the size of the temp trace files. Make sure you have plenty of free space in your C drive as well.

UWP/WinRT: App stopped working after November update

I have a Universal Windows Platform app that was working fine. My development machine is running Windows 10, and after the Windows 10 November Update (1511, build 10586), the development version built by Visual Studio has stopped working. I was actually running this day-to-day as a standalone app, and I noticed this problem when after the update the app started immediately closing after the splash screen.
I uninstalled the development version of my app and installed the store version, and that works fine, even though no code has changed between the two versions. I updated Visual Studio to Update 1, and it still doesn't work. I've fully uninstalled and reinstalled Visual Studio but that didn't help either. I've also tried changing the Project Properties to target platform version 10.0.10586.0 and rebuilding, but that also doesn't seem to help.
This occurs on both Release and Debug builds, and on both x86 and x64.
On launch, it gets as far as the splash screen before informing me that I've triggered a breakpoint. The breakpoint was not set by me, but rather is in KernelBase.dll, and no source is available.
If I hit Continue, then I get an Unhandled exception at 0x00007FFC4C431F08 (KernelBase.dll). The body of the error is:
0x00000004: The system cannot open the file (parameters: 0xFFFFFFFF80004005, 0x0000000000000005).
Hitting Continue again will get me into my code, which dies with:
Microsoft C++ exception: Platform::COMException ^ at memory location 0x000000C1517FAF50. HRESULT:0x802B000A The text associated with this error code could not be found.
Any ideas on what happened and how to correct?

Can't run VS 2015 Community without /resetsettings; Getting CANTLOADLIBRARY on opening new projects, and crashing on new .cpp files

I have Windows 10, fully updated.
I downloaded and installed Visual Studio Community 2015 last week for the first time, (previously programmed in Code:blocks, still installed) and selected custom install to allow for C++ and Python programming.
Installation ran smoothly, but VS always fails on launch.
On first launch ever, it said it was setting things up for first startup; asked me for sign-in which I did, at which point it briefly showed something about my profile before saying 'An error occurred while starting for the first time. Please restart Microsoft Visual Studio'. Imgur images of all dialog boxes here, including parts of a processmonitor log I estimated to be around the general time of the error.
Closing and restarting several times didn't help.
Uninstalling and re-installing didn't help.
Rebooting didn't help.
And uninstalling, running Ccleaner's Cleaner and Registry Cleaner, rebooting computer and re-installing VS didn't help either.
Repairing the install from Programs also didn't help.
I managed to find the exact same error on Google Search for VS 2013 but the only solution was where one person got a completely new OS and re-installed VS on that.
I tried the other suggestions they had including running:
devenv.exe /safemode
devenv.exe /resetskippkgs
devenv.exe /resetuserdata
devenv.exe /installvstemplates
devenv.exe /resetsettings
the first 3 took me to the same sign-in screen. Regardless of signing-in or not, or running VS from the Administrator Profile or not, these option always give the same failed on first startup error.
Installvstemplates gives an error saying the operation could not be completed, but /resetsettings finally got me into VS.
That's about all it does though, I can go to the home page and access options/menu buttons, but signing-in makes it crash and reload again (but it does sign me in and take me to the home screen)
Signed-in/not and Administrator or not, VS crashes on opening a new .cpp file.
When I click Start a New Project I get "Error loading type library/DLL.(Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)). Closing VS and trying to open it normally from start menu still always throws the original error, despite working if I open it via /resetsettings.
I've also checked [HKEY_CLASSES_ROOT\CLSID{73B7DC00-F498-4ABD-AB79-D07AFD52F395}\InProcServer32] in Regedit and found it is apparently correct.
I also used devenv /log to generate an xml file of the process when I open it.
Just to mention I have .NET Framework 4.5-4.6 installed with VS as well.
Looking forward to any advice.
So, for anyone else getting the same problem, I haven't gotten any other advice, since this post.
If you're still having probs # this point the only real solution seems to be a clean install of your OS .
I can confirm it solved all my issues, with VS + some OS problems I wasn't aware of . I can only assume they might've been related, good luck.

Visual Studio 2015 error: Unable to start debugging. Unexpected GDB output from command "-target-select remote :5039". Remote connection closed

I see the following error whenever I try to debug "Cross Platform" under "C++" category: "Unable to start debugging. Unexpected GDB output from command "-target-select remote :5039". Remote connection closed"
I've installed all of the contents when I downloaded Visual Studio 2015 community and I ran it on Windows 10 Pro which supports Hyper-V.
I've been searching a solution for this and I've found an assumption:
"What is your debug target, the VS Android Emulator? When we saw this before it turned out to be a bad emulator image. Do you have this problem with all targets (e.g. if you try a physical device) or just one?"
In my case, I just tried this via Emulator(VS Emulator 5" Lolipop (5.0) XXHDP Phone (0x86 -...)
So I've sent an Email to VS 2015.
And the answer was like this:
"Sorry for the delay in responding we were looking at an emulator image of another user that ran into this problem so I was waiting until we had the results of that investigation to report back. We actually were not able to find anything wrong the emulator itself, our current hypothesis is that it is a network or adb problem interfering with GDB’s ability to connect to GDB server on the remote machine. Do you see this error every time you try to debug, or if you reboot the emulator will it work sometimes right after the reboot? Next time you see the error, can you open the emulator’s console mode by going go the Hyper-V manager and double clicking the emulator. Then find the location your app installed to and run “gdbserver --version" from the app path and let me know what it says? This will validate if the correct version of gdbserver is on the device."
So we are trying to solve this problem but I'm also asking here just in case.
Is there anyone who has magical solution for this problem?
I'll put a comment on this if I figure out how to solve this.
Thanks in advance.
** Following answer is from the manager of Visual Studio 2015:
You are only the second person who has run into this issue, and the first person that ran into it provided their everything works correctly when we run their .vhd on our machines so it appears to be some strange problem where gdbserver (which comes from the Android NDK provided by Google) crashes only when running on certain machines. Unfortunately the .vhd you provided does not appear to be the correct one it won’t boot for me. You can see the .vhd file being used by the emulator if you look under the settings of the emulator in your Hyper-V manager. .However given we got the other person’s .vhd you can hold off providing any additional information at this point. I’m waiting to hear back from the emulator team on if they have any ideas since this appears to be an issue only on specific machines since.
If you don’t mind my asking, if you don’t have a background in computers what inspired you to try C++ on Android? That scenario will be significantly more complicated than doing Java on Android.
It's been almost two months since I got this answer but I haven't got any additional response from them yet. So, I ended up quitting developing an application by using VS2015.
If you run into this problem, there are only two ways to go. Change your computer or stop developing application via VS2015.
If the project name contains spaces, the whole remote debugging fails. Visual Studio also creates weird paths. When checking out the "Blink1 for Raspberry Pi" template, I named the Project "Blink1 for Pi", which resulted in a path like this:
~/projects/Blink1?/for/pi/PI/for/pi....
And all the debugging failed. When I recreated this keeping the project name "Blink1", everything worked fine. It's a pity, that spaces aren't handled here...

Genymotion emulator crashes on Windows 7 machine when running calabash-android tests

I am using Genymotion emulator to run my calabash android tests. I have around 7 feature files and after successfully running 3-4 features geny motion crashes with the following exception:
"Player.exe has stopped working"
"Microsoft Visual c++ runtime Library
The application has requested the runtime to terminate it in an unusual way"
Unfortunately I am not able to post the images for this post.
Has anybody got a fix for this?
Thanks in advance!
-Nishi