spyder: kernel not starting and high CPU usage on Apple M1
Problem Description
When launching Spyder on MacBook Pro with apple M1. The consol tries to connect to the kernel without succeeding and the CPU usage of symptomsd and python are uncommonly high (from 80% to 180%)
What steps reproduce the problem?
- launch Spyder
Versions
- Spyder version: 5.1.1
- Python version: tested on 3.9.5 Internal / 3.9.6 custom
- Qt version: 5.12.10
- PyQt version: 5.12.3
- Operating System name/version: macOS 11.5.2
Dependencies
# Mandatory:
applaunchservices >=0.1.7 : 0.2.1 (OK)
atomicwrites >=1.2.0 : 1.4.0 (OK)
chardet >=2.0.0 : 4.0.0 (OK)
cloudpickle >=0.5.0 : 1.6.0 (OK)
cookiecutter >=1.6.0 : 1.7.3 (OK)
diff_match_patch >=20181111 : 20200713 (OK)
intervaltree >=3.0.2 : 3.1.0 (OK)
IPython >=7.6.0 : 7.26.0 (OK)
jedi >=0.17.2;<0.19.0 : 0.18.0 (OK)
jsonschema >=3.2.0 : 3.2.0 (OK)
keyring >=17.0.0 : 23.0.1 (OK)
nbconvert >=4.0 : 6.1.0 (OK)
numpydoc >=0.6.0 : 1.1.0 (OK)
parso >=0.7.0;<0.9.0 : 0.8.2 (OK)
pexpect >=4.4.0 : 4.8.0 (OK)
pickleshare >=0.4 : 0.7.5 (OK)
psutil >=5.3 : 5.8.0 (OK)
pygments >=2.0 : 2.9.0 (OK)
pylint >=2.5.0 : 2.9.6 (OK)
pyls_spyder >=0.4.0 : 0.4.0 (OK)
pylsp >=1.2.1;<1.3.0 : 1.2.1 (OK)
pylsp_black >=1.0.0 : None (OK)
qdarkstyle =3.0.2 : 3.0.2 (OK)
qstylizer >=0.1.10 : 0.2.1 (OK)
qtawesome >=1.0.2 : 1.0.3 (OK)
qtconsole >=5.1.0 : 5.1.1 (OK)
qtpy >=1.5.0 : 1.9.0 (OK)
rtree >=0.9.7 : 0.9.7 (OK)
setuptools >=49.6.0 : 57.4.0 (OK)
sphinx >=0.6.6 : 4.1.2 (OK)
spyder_kernels >=2.1.0;<2.2.0 : 2.1.0 (OK)
textdistance >=4.2.0 : 4.2.1 (OK)
three_merge >=0.1.1 : 0.1.1 (OK)
watchdog >=0.10.3 : 2.1.3 (OK)
zmq >=17 : 22.2.0 (OK)
# Optional:
cython >=0.21 : 0.29.24 (OK)
matplotlib >=2.0.0 : 3.4.2 (OK)
numpy >=1.7 : 1.21.1 (OK)
pandas >=1.1.1 : 1.3.1 (OK)
scipy >=0.17.0 : 1.7.1 (OK)
sympy >=0.7.3 : 1.8 (OK)
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 17 (9 by maintainers)
Just desperately tried to reboot my computer (which I never do since new Mac chip manages power consumption well in sleep mode). It took more time than usual to reboot (dunno why) but Spyder restarted working. Sometimes I don’t try to understand. However I think this could show that a task on my computer is doing shit and could do it again. I will try to inspect the tasks that are running. Anyway thanks a lot for your support and your patience 😃