Python Forum

Full Version: Error: python.exe application error
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I run my application through PyCharm.
I get an error on closing my application:
'python.exe application error the instruction at "0x6703e506" referenced memory at "0x0000000". The memory could not be read'

I get this message the past 3 - 4 days, till then no message showed up.
How can I find what causes the error?
What happens if you just run it from the command terminal?  If you still get an error, please post the entire Traceback and any relevant code.
I run it from the cmd, but I don't get this error!
I get another one, not on closing of the application, but when I click a combo box:
[attachment=108]

This error was caused by some non-latin characters in my string, I removed them and it's ok, I suppose it's a matter of character encoding.
Anyway, it's irrelevant to the 'python.exe application error'.

Conclusion is, the 'python.exe application error' doesn't appear when I run it in the command line, only when I run it with PyCharm.
Which version of python are you running?
If 2.7 or earlier, you must specifically tell the script that you are using UTF-8 (or any other version of UTF).
In Python 3 and above it's automatically taken into consideration.

Yet another reason to use a modern version of Python
Quote:Conclusion is, the 'python.exe application error' doesn't appear when I run it in the command line, only when I run it with PyCharm.


Yes, there are certain instances when a script will not run as expected in Pycharm's default terminal.  You can switch to the command terminal (View --> Tool Windows --> Terminal), or just open a command terminal and run your script to verify whether it is Pycharm or the script that is causing the error.  It's only happened to me two, maybe three times, but it does happen.
(Jan-14-2017, 01:23 PM)Larz60+ Wrote: [ -> ]Which version of python are you running?

It's Python 3.4.


So, while it doesn't happen with the windows terminal, I 'll consider it's not a real error.
Thank you!