New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pyscripter randomly locks up - still #1124
Comments
Could you please try version 4 and report if the issue still occurs? |
I used 3.x alot and got a hanging PyScripter from time to time, really very seldom. |
I have also been using Pyscripter for years and it constantly locks up. I am also sick of upgrading versions to no avail. Seeing that "Reinitialize Python Engine" does not work anymore which should be a solution can you please at LEAST save the open tabs when you open a file. At least that will save the state of Pyscripter so I don't feel like uninstalling it every time this happens to me and then use VS Code like everyone else who is tired of flaky IDEs. |
I am very keen to address this issue. But I need steps to reproduce it. Once I get a way of reproducing it I can provide a proper fix. |
I was simply debugging and editing a simple file which was using only a few python modules , I locked my computer and after I came back to it, PS was frozen again. It was still in debug mode which always seems to cause it, and whenever I try to actually type variable names to see values in the console output I am scared it will result in a lockup. Complex variables seem to trigger it. Its obvious to me its a debugging data passing/connection issue with the remserver.py. I also don't know why PS needs 3 separate python processes. I would like Pyscripter to be solid like it was in the past, I actually like that it was built using Delphi, I even was trying to compile it way back to solve this issue but ran out of time. Just give us a button that says kill all python.exe child processes so you can at least stay in the IDE and not want to smash things when every file you had open is lost. |
So the crash happens when
Is this correct? If you don't use the interpreter window while debugging then there are no crashes. By the way you can hover the mouse over variable names in the editor to see values. Does this also result in crashes? Please also confirm that you are using the latest version. Is it possible to share one of the scripts in which you see crashes? Even better if you specify the steps that led to the crash. (i.e. I set a breakpoint at line x, and when I hit the breakpoint, I typed xyz in the editor). |
Hover over vars for values does work and I use it. I also tend to leave PS open permanently as I had crashes in the past just closing it so I don't like losing the current state of the tabs , app and window settings. I have tried changing settings in the past .... autocompletion, variable hover, file change values, but nothing ever seemed to fix it. |
|
I was using the ldap3 module at the time which is used in a lot of the code I work on, and I can not share it for business reasons. |
ldap3 uses sockets and may be some strange interaction with the TCP/IP connections PyScripter uses. Do you see crashes with scripts not using ldap3? One thing to try:
PyScripter can interact with the debugged program using Windows pipes. Please report whether this makes things better. This should also be faster. |
Thanks I will try that |
I did try that after another crash but now if I run code I am working on using import win32pipe, win32file, pywintypes |
Strange
Could you please provide a minimal script that fails to run? |
This is a continuation of #641
This random "not responding" problem has been happening for the last 4 years. It happens several times an hour.
It is now 2021 and this problem still happens in Pyscripter 3.6.4.0 x64 and Python 3.9
The "solution" seems to be always "upgrade to latest version". This action, at no time, has prevented this error happening again. I have tried all the "tweaks" that people have suggested.
I have been trying to use Pyscripter for many many years, and like what it does in general. It is this problem that has forced me to move on to other IDE's that are more stable.
I hope you are able to solve it, otherwise I cannot recommend it to all my students.
The text was updated successfully, but these errors were encountered: