-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Spyder unresponsive, requires forced quit (OS X) #3306
Comments
I have experienced the exact same issue repeatedly. Something I can add is that when I'm using matplotlib, there is an extra icon that shows up in the dock (just named "python") which is where the figure windows go. When I checked thismorning after sleeping the computer overnight, I had the spinning wheel issue, but I also had three instances of the matplotlib icon in the dock for some reason. |
This was supposedly fixed in beta4, but that doesn't seem to be the case. Something you can do to help us solve this problem is to open Spyder from a terminal, but not as a background process, i.e. as
instead of
Then when the freeze occurs, you need to press |
@blink1073, could you take a look at this one? This is the same problem as before :-) |
I got exactly the same traceback, using 3.0.0b4 Also, I got this error in the terminal after the first ctrl-c
|
I am unable to reproduce this from either the latest master or |
Also tried with Python 2.7.11. @ccordoba12, can you reproduce? |
My experience is that this behaviour takes a bit of time to kick in. If you can't reproduce from a sleep/wake, my suggestion would be to leave spyder running overnight in the background and check it in the morning. My reproducible steps are:
I'm running 3.0.0b4 with python 3.5.2 and ipython 4.2.0 (latest anaconda update) on OSX 10.11.5 |
Thanks @Keou0007, I'll try that tonight. |
Hey guys, could you update to Spyder master and try again? We just merged pull request #3325, which could help to solve this problem. Thanks ;-) |
I ran it overnight with #3325 applied. The program was still responsive, but the introspection itself was not working, and repeatedly printing the message below in the terminal (note that I have DEBUG mode set). I'm not yet sure what to do about it.
|
I'm on beta 4, installed via conda. I can't seem to find a way to install the github master through conda. Am I missing something? |
Hi @Keou0007, conda is for released bundles only. Using a git checkout is an entirely different process. You |
I figured it would be something like that, thanks. Done it now. I'll leave it overnight and see what happens. |
I tried to launch spyder directly in terminal. Sometime it gave me |
That's unimportant and not relevant to this issue. |
all right, I will keep tracking it. |
Could anyone else confirm that this issue is fixed in master? |
I can't sure. Because some lags happened when I launched it within the anaconda navigator, but not in terminal. |
I was experiencing this bug on beta3. |
I have left the master overnight and come back to it responsive. This is an obvious improvement over beta 4, BUT I've had problems loading scipy with the master, so I haven't been able to do any actual work with it, just open it and let it sit. As such, I'd be hesitant to say for certain that it's fixed, incase it is something else I usually load up (scipy, Numpy, matplotlib, seaborn, etc) that's also causing the issue. |
Please open a new issue about this. |
Given this confirmation (besides the one from @blink1073), I consider this issue solved. |
The behavior I'm seeing is that the introspection can fail, but it is no longer bringing down the application. At least you can save state and restart to get introspection back. I'll dig some more to see if I can eke out more stability. |
Thanks @blink1073! I hope you can find time to work on this soon because I'm thinking to release beta5 after you solve the bug about introspection not working on Mac after resumes (I can confirm this is not a problem on Windows and Linux). There are already important issues solved in master (e.g. profiler is missing in beta4) that deserve a new beta :-) |
are you sure that it is an error ? It seems to me more like a warning |
I've got a similar one while syncing a digibyte-qt on my mac : DigiByte-Qt[86726] : void CGSUpdateManager::log() const: conn 0x1020b: spurious update |
Description of your problem
What steps will reproduce the problem?
Versions and main components
Dependencies
jedi >=0.8.1 : 0.9.0 (OK)
matplotlib >=1.0 : 1.4.3 (OK)
nbconvert >=4.0 : 4.2.0 (OK)
numpy >=1.7 : 1.9.2 (OK)
pandas >=0.13.1 : None (NOK)
pep8 >=0.6 : 1.7.0 (OK)
psutil >=0.3 : 4.3.0 (OK)
pyflakes >=0.5.0 : 1.2.3 (OK)
pygments >=2.0 : 2.1.3 (OK)
qtconsole >=4.2.0: 4.2.1 (OK)
rope >=0.9.4 : 0.9.4 (OK)
sphinx >=0.6.6 : 1.4.1 (OK)
sympy >=0.7.3 : None (NOK)
PyQt = 5.6
Qt = 5.6.0
The text was updated successfully, but these errors were encountered: