PyScripter Post-Crash Message: "Access violation at address 0085B9EC in module 'PyScripter.exe'. Read of address 00000418."

1,003 views
Skip to first unread message

Yatharth Agarwal

unread,
Feb 22, 2012, 9:20:47 AM2/22/12
to pyscr...@googlegroups.com
I accidentally ran a file with an infinite loop with the Internal Python Engine and PyScripter showed "Can't re-initialize/change python engine while running." or something.  I pressed Ctrl+Alt+Del and force-closed PyScripter using Task Manager. 
Now, whenever I click PyScripter, it does'nt respond; and when I log off, it shows "No Python Engine created." and then "Access violation at address 0085B9EC in module 'PyScripter.exe'. Read of address 00000418."

PyScripter

unread,
Feb 22, 2012, 10:03:39 AM2/22/12
to pyscr...@googlegroups.com
Which version of PyScripter are you using?  Are you sure you were using the internal Python engine?  (not recommended).  If not there may be a process of the remote python engine in the task manager which appears as pythonw.exe.   In any case a reboot should solve the problem.

Yatharth Agarwal

unread,
Feb 25, 2012, 10:08:46 AM2/25/12
to pyscr...@googlegroups.com
On Wednesday, February 22, 2012 6:03:39 PM UTC+3, PyScripter wrote:
Which version of PyScripter are you using?  Are you sure you were using the internal Python engine?  (not recommended).  If not there may be a process of the remote python engine in the task manager which appears as pythonw.exe.   In any case a reboot should solve the problem.

I'm using version 2.4.3 (I think I checked some option like "Check for updates every 7 days" or something, so I think it should be the latest version). Yeah, I'm sure I was running the internal python engine. I was using it cuz' I didn't want to re-initialize the engine every time I ran the file. I tried re-booting, but that didn't do anything. In Task Manager, it does show a process "PyScripter.exe - PyScripter Python IDE" but nothing else. I'm going to try to re-install PyScripter on my system now.

Yatharth Agarwal

unread,
Feb 25, 2012, 10:31:10 AM2/25/12
to pyscr...@googlegroups.com
I re-installed PyScripter, replaced the .ini file with the previous one, and opened PyScripter. All was well and everything worked till I created two more shortcuts with the same path but different flags (atleast that's what I think they're called). One had --PYTHON27 appended to it and the other --PYTHON32. Now when I try to open PyScripter from either of them, nothing happens like before; and when I try to log off it shows the same errors from before. Help !!!

PyScripter

unread,
Feb 25, 2012, 10:39:44 AM2/25/12
to pyscr...@googlegroups.com
Did you install PyScripter using the provided setup file?
If yes, the setup file creates a number of shortcut one for each supported version of Python.  Why do you need to create other shortcuts?
When you run PyScripter (Latest Python version), which version of Python does PyScripter loads?  (you can see that in the interpreter window.

The reason that PyScripter fails when used with some --pythonxx command line parameter, is that it cannot find and load that version of python.
Reply all
Reply to author
Forward
0 new messages