FS#49277 - [ipython] sometimes segfaults.

Attached to Project: Community Packages
Opened by ole (olejorgenb) - Monday, 09 May 2016, 17:26 GMT
Last edited by Balló György (City-busz) - Sunday, 01 September 2019, 10:28 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Kyle Keen (keenerd)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Might be related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741555

Additional info:
pacman -Qi ipython
Name : ipython
Version : 4.1.2-2

Steps to reproduce:
Not entirely sure. Happens from time to time though..

Removing ~/.ipython fixes the issue for a while
This task depends upon

Closed by  Balló György (City-busz)
Sunday, 01 September 2019, 10:28 GMT
Reason for closing:  No response
Comment by ole (olejorgenb) - Monday, 09 May 2016, 17:28 GMT
Possible also: https://github.com/ipython/ipython/issues/5260
Comment by Kyle Keen (keenerd) - Monday, 09 May 2016, 17:49 GMT
Those are both from two years ago, and were fixed. I doubt it is the exact same issue this time around. Not closing.

Do try to pin down the behavior that causes it. Can any of the previously mentioned triggers cause the crash for you?
Comment by ole (olejorgenb) - Friday, 20 May 2016, 09:13 GMT
I haven't been able to reproduce reliably. It might have something to do with emacs though. I use spacemacs which uses ipython as its default python interpreter. I have another machine (running nixos) that don't have the problem though.

It's quite annoying, just now, I wasted 20min debugging emacs hanging - turns out it's due to ipython crashing (emacs hanging because of that is a bug in itself of course)

In case anyone have the same issue with emacs they might find this ticket if I include:
Making python-shell-interpreter local to *Python Internal [c0593018489da24980655d141e87046c]* while let-bound!
Comment by Bruno Pagani (ArchangeGabriel) - Wednesday, 31 October 2018, 13:52 GMT
Does that issue still exists?

Loading...