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.

Memory access error (memory dumped) when try to start spyder

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

Problem Description

The error occur when I start Spyder with the terminal or with the Anaconda Navigator. Spyder don’t start and in the terminal the error message occur.

What steps reproduce the problem?

  1. Start Spyder with the terminal
  2. Start Spyder with the Anaconda Navigator
  3. Start the Qtconsole with the Anaconda Navigator

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

I want to start Spyder, instead it don’t start and in the terminal an error message is shown.

Paste Traceback/Error Below (if applicable)


/home/mattes/.anaconda/navigator/scripts/gmt-python/spyder.sh: Zeile 3:  6197 Speicherzugriffsfehler  (Speicherabzug geschrieben) spyder > /home/mattes/.anaconda/navigator/scripts/gmt-python/spyder-out-2.txt 2> /home/mattes/.anaconda/navigator/scripts/gmt-python/spyder-err-2.txt


Speicherzugriffsfehler (Speicherabzug geschrieben) = Memory access error (memory dumped)

Versions

  • Spyder version: 3.2.8
  • Python version: 3.6.3
  • Qt version: 5.6.2
  • PyQt version: 5.6.0
  • Operating System name/version: Ubuntu 16.04

Dependencies


Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
DennisScubacommented, Jun 7, 2018

Thank you very much for the fast reply, the installation of pyopengl didn’t worked but when I switched to qt/pyqt 5.9 it worked! Thanks a lot for your help!

1reaction
CAM-Gerlachcommented, Jun 7, 2018

Thanks for your detailed reply.

When I try to start the qtconsole with the Anaconda Navigator inside the environment, this error occurs:

Okay, so this means that the problem has something to do with your Anaconda install. not Spyder, since its affecting other applications and thus out of our control.

Two things to try, before going ahead with the more dramatic suggestions in the Troubleshooting guide (like reinstalling Anaconda):

  • Install pyopengl in your environment, e.g. with conda install pyopengl while the environment is activated, and try launching Spyder again
  • Switch to qt/pyqt 5.9, with conda install pyqt=5.9. Usually the other way around is more reliable right now, but you never know…

Other than that, something in the troubleshooting guide should get you up and running again unless there is some issue with your machine.

Best of luck!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Complete Guide to Python Memory Error - eduCBA
Guide to Python Memory Error. Here we discuss the introduction, working and avoiding memory errors in python respectively.
Read more >
Dying, fast and slow: out-of-memory crashes in Python
When your computer's RAM fills up, the operating system will start moving chunks of memory out of RAM and on to your disk,...
Read more >
Spyder does not release memory for matplotlib plots
For me, using gc.collect resolved the issue. I am using: Spyder 3.3.6, Python 3.7.6, Ipython 7.11.1. Minimal working/crashing example.
Read more >
How to Solve Memory Error in Python
A memory error means that your program has run out of memory. This means that your program somehow creates too many objects. In...
Read more >
How to Fix Memory Leaks in Python? - Section.io
With a lack of space, the program may be destroyed or starts working ... Python developers have tried to address memory leaks through...
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