Skip to content
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

Closed
durack1 opened this issue Jul 19, 2016 · 27 comments
Closed

Spyder unresponsive, requires forced quit (OS X) #3306

durack1 opened this issue Jul 19, 2016 · 27 comments
Assignees
Milestone

Comments

@durack1
Copy link

durack1 commented Jul 19, 2016

Description of your problem

What steps will reproduce the problem?

  1. Open spyder 3.0.0beta4 (anaconda installation on OS X 10.11.5)
  2. Start using the console
  3. Stop input for the machine so that the screensaver/lockout occurs
  4. Upon login the Spyder console is unresponsive and I get a rainbow spinning wheel of death
  5. The only option is to terminate the inactive session (force quit on OS X)
    deadspyder

Versions and main components

  • Spyder Version: 3.0.0beta4
  • Python Version: Python 2.7.11 |Continuum Analytics, Inc.| (default, Dec 6 2015, 18:57:58)
  • Operating system: OS X 10.11.5

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

@Keou0007
Copy link
Contributor

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.

@ccordoba12
Copy link
Member

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

spyder

instead of

spyder &

Then when the freeze occurs, you need to press Ctrl+C in the terminal. This should generate a traceback in Spyder's internal console, which you can copy and paste here.

@qingkaikong
Copy link

qingkaikong commented Jul 23, 2016

This is the traceback after I press Ctrl+C, but due to the IDE frozen, I can not scroll up, so I just took a screenshot here: BTW, it seems I am using spyder 3.0.0.dev0, I will update to the latest version, and test it.

screen shot 2016-07-23 at 9 02 37 am

@ccordoba12
Copy link
Member

@blink1073, could you take a look at this one? This is the same problem as before :-)

@Keou0007
Copy link
Contributor

I got exactly the same traceback, using 3.0.0b4
Same deal, spinning wheel meant I couldn't scroll or copy/paste the traceback.

Also, I got this error in the terminal after the first ctrl-c

^CJul 24 18:43:24 python[92786] <Warning>: void CGSUpdateManager::log() const: conn 0x31c9f: spurious update.

@blink1073
Copy link
Contributor

I am unable to reproduce this from either the latest master or v3.0.0b4. I can hit Ctrl+C just fine in the terminal when run as bootstrap.py or using the spyder command, and a forced sleep/wake up has no effect. I am using Python 3.4.5 anaconda on OSX 10.11.6. My pyzmq is v15.3.0.

@blink1073
Copy link
Contributor

Also tried with Python 2.7.11. @ccordoba12, can you reproduce?

@Keou0007
Copy link
Contributor

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:

  1. Open spyder
  2. sleep computer overnight
  3. wake computer in morning
  4. spinning wheel on spyder, if run from terminal, ctrl-c in terminal produces the traceback above in the internal console window in spyder, and then the spinning wheel comes back.

I'm running 3.0.0b4 with python 3.5.2 and ipython 4.2.0 (latest anaconda update) on OSX 10.11.5

@blink1073
Copy link
Contributor

Thanks @Keou0007, I'll try that tonight.

@ccordoba12
Copy link
Member

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 ;-)

@ccordoba12 ccordoba12 added this to the v3.0beta5 milestone Jul 26, 2016
@ccordoba12 ccordoba12 changed the title Spinning wheel on unresponsive spyder console - requires forced quit (OS X) Spyder unresponsive, requires forced quit (OS X) Jul 26, 2016
@blink1073
Copy link
Contributor

blink1073 commented Jul 26, 2016

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.

Resource temporarily unavailable
Errored rope
b''
b''
Resource temporarily unavailable
Errored jedi
b''
b''
Resource temporarily unavailable
Errored fallback
b''
b''

@Keou0007
Copy link
Contributor

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?

@blink1073
Copy link
Contributor

Hi @Keou0007, conda is for released bundles only. Using a git checkout is an entirely different process. You git clone this repository, then run python bootstrap.py from the repository directory to run that version of spyder.

@Keou0007
Copy link
Contributor

I figured it would be something like that, thanks. Done it now. I'll leave it overnight and see what happens.

@jiangxiluning
Copy link

I tried to launch spyder directly in terminal. Sometime it gave me
QNSView mouseDragged: Internal mouse button tracking invalid (missing Qt::LeftButton)

@ccordoba12
Copy link
Member

That's unimportant and not relevant to this issue.

@jiangxiluning
Copy link

all right, I will keep tracking it.

@ccordoba12
Copy link
Member

Could anyone else confirm that this issue is fixed in master?

@jiangxiluning
Copy link

I can't sure. Because some lags happened when I launched it within the anaconda navigator, but not in terminal.

@ghost
Copy link

ghost commented Jul 28, 2016

I was experiencing this bug on beta3.
Got beta4 yesterday, and it seems to be fine now :)

@Keou0007
Copy link
Contributor

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.

@ccordoba12
Copy link
Member

BUT I've had problems loading scipy with the master

Please open a new issue about this.

@ccordoba12
Copy link
Member

I have left the master overnight and come back to it responsive.

Given this confirmation (besides the one from @blink1073), I consider this issue solved.

@blink1073
Copy link
Contributor

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.

@ccordoba12
Copy link
Member

ccordoba12 commented Jul 29, 2016

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 :-)

@mrntidu
Copy link

mrntidu commented Mar 28, 2018

are you sure that it is an error ? It seems to me more like a warning

@mrntidu
Copy link

mrntidu commented Mar 28, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants