question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Spyder crashes with Segmentation fault: 11 when Mac goes to sleep

See original GitHub issue

Issue Report Checklist

  • Searched the issues page for similar reports
  • Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
  • Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
  • Could not reproduce inside jupyter qtconsole (if console-related)
  • Tried basic troubleshooting (if a bug/error)
    • Restarted Spyder
    • Reset preferences with spyder --reset
    • Reinstalled the latest version of Anaconda
    • Tried the other applicable steps from the Troubleshooting Guide
  • Completed the Problem Description, Steps to Reproduce and Version sections below

Hello - I’ve seen some similar issues like, but nothing that exactly fits what I’m experiencing.

Problem Description

spyder crashes when computer goes to sleep. Error message is segmentation fault: 11

What steps reproduce the problem?

  1. Launch spyder from terminal spyder3
  2. Everything is fine all day as I’m using it.
  3. Close laptop, computer goes to sleep.
  4. Come back the next day, spyder has crashed, with the message Segmentation fault: 11 in the terminal.
  5. This happens every day

What is the expected output? What do you see instead?

I expect it not to happen

Paste Traceback/Error Below (if applicable)


Since spyder has crashed, there are no logs to copy.

Versions

  • Spyder version: 4.1.4
  • Python version: 3.7.7
  • Qt version: 5.12.9
  • PyQt version: 5.12.3
  • Operating System name/version: MacOS Catalina 10.15.6

Dependencies


# Mandatory:
applaunchservices >=0.1.7      :  0.2.1 (OK)
atomicwrites >=1.2.0           :  1.4.0 (OK)
chardet >=2.0.0                :  3.0.4 (OK)
cloudpickle >=0.5.0            :  1.5.0 (OK)
diff_match_patch >=20181111    :  20200713 (OK)
intervaltree                   :  None (OK)
IPython >=4.0                  :  7.16.1 (OK)
jedi =0.17.1                   :  0.17.1 (OK)
nbconvert >=4.0                :  5.6.1 (OK)
numpydoc >=0.6.0               :  1.1.0 (OK)
parso =0.7.0                   :  0.7.0 (OK)
pexpect >=4.4.0                :  4.8.0 (OK)
pickleshare >=0.4              :  0.7.5 (OK)
psutil >=5.3                   :  5.7.2 (OK)
pygments >=2.0                 :  2.6.1 (OK)
pylint >=1.0                   :  2.5.3 (OK)
pyls >=0.34.0;<1.0.0           :  0.34.1 (OK)
qdarkstyle >=2.8               :  2.8.1 (OK)
qtawesome >=0.5.7              :  0.7.2 (OK)
qtconsole >=4.6.0              :  4.7.5 (OK)
qtpy >=1.5.0                   :  1.9.0 (OK)
sphinx >=0.6.6                 :  3.1.2 (OK)
spyder_kernels >=1.9.2;<1.10.0 :  1.9.2 (OK)
watchdog                       :  None (OK)
zmq >=17                       :  19.0.1 (OK)

# Optional:
cython >=0.21                  :  None (OK)
matplotlib >=2.0.0             :  None (OK)
numpy >=1.7                    :  1.19.0 (OK)
pandas >=0.13.1                :  1.0.5 (OK)
scipy >=0.17.0                 :  1.5.1 (OK)
sympy >=0.7.3                  :  None (OK)

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:11 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
laurajanemcommented, Aug 19, 2020

Sure, that’s fine.

On Wed, Aug 19, 2020 at 6:15 PM Carlos Cordoba notifications@github.com wrote:

@laurajanem https://github.com/laurajanem, since there’s nothing else we can do at the moment and you’re unable to use Anaconda (which is our recommended installation method), is it ok if we close this issue?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spyder-ide/spyder/issues/13570#issuecomment-676757077, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEFQKPMY76ZA2AWZU7FHDPTSBRFJVANCNFSM4QE7GX6Q .

0reactions
ccordoba12commented, Aug 19, 2020

@laurajanem, since there’s nothing else we can do at the moment and you’re unable to use Anaconda (which is our recommended installation method), is it ok if we close this issue?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Spyder anaconda crashes on Linux with segmentation fault
(Spyder maintainer here) This problem is caused by faulty graphical card drivers and there are two ways to fix it: Update to Spyder...
Read more >
Bug listing with status RESOLVED with resolution OBSOLETE ...
... Bug:286046 - "sys-apps/hal-0.5.11-r9 hald segfault when initializing RAID partition block device" status:RESOLVED resolution:OBSOLETE severity:major ...
Read more >
[SOLVED] "Segmentation fault" running a Python3 script
When temp drops, it turns off. I have sort of mashed up the following two scripts, to try get where I am trying...
Read more >
Watchdog - PyPI
Watchdog comes with an optional utility script called watchmedo. ... [mac] Fix a segmentation fault when dealing with unicode paths (#763).
Read more >
PGQ - River Thames Conditions
Jongkey 2013 tumblr, Us pows return from vietnam, Bases of market segmentation ppt, Kamikaz freestyle skyrock, Kings sixth form gloucester, Sharvesh travels ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found