Random segfaults

[spyder-bot]

From contrebasse on 2014-03-18T04:08:22Z

Spyder Version: 2.3.0dev (3531: ra08d6bcfa38a )
Python Version: 2.7.6
Qt Version : 4.8.5, PySide 1.2.1 on Linux
IPython >=0.13 : 1.2.1 (OK)
pyflakes >=0.5.0: 0.5.0 (OK)
pep8 >=0.6 : 1.4.6 (OK)
sphinx >=0.6.6 : 1.2.1 (OK)
rope >=0.9.2 : 0.9.4 (OK)
matplotlib >=1.0: 1.3.1 (OK)
sympy >=0.7.0 : 0.7.5 (OK)
pylint >=0.25 : 1.1.0 (OK)

What steps will reproduce the problem?

1. Edit text What is the expected output? What do you see instead? From time to time, spyder segfaults while editing text (3 or 4 times a day). I'll try go get a core dump next time.

Please provide any additional information below

.

Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1758

[spyder-bot]

From contrebasse on 2014-05-09T12:20:41Z

This happened with pyside but not with pyqt. It didn't happen for a while, though.

[spyder-bot]

From ccordoba12 on 2014-05-10T06:48:03Z

Can we close it then?

[spyder-bot]

From contrebasse on 2014-05-10T11:28:04Z

Yes, I'll comment again if it comes back eventually.

[spyder-bot]

From contrebasse on 2014-05-12T08:07:18Z

Meh, just happened again.

[spyder-bot]

From contrebasse on 2014-05-12T08:41:35Z

J'ai lancé "gdb -ex r --args python2 bootstrap.py" et ça donne ça: (pyside est pas compilé avec les symboles de debug par contre):

[New Thread 0x7fff59172700 (LWP 5008)]

Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0x7fff59172700 (LWP 5008)]
0x00007ffff780cefb in send () from /usr/lib/libpthread.so.0
(gdb) bt
#0 0x00007ffff780cefb in send () from /usr/lib/libpthread.so.0
#1 0x00007ffff230608e in ?? () from /usr/lib/python2.7/lib-dynload/_socket.so
#2 0x00007ffff7af79f4 in PyEval_EvalFrameEx ()
from /usr/lib/libpython2.7.so.1.0
#3 0x00007ffff7af91b0 in PyEval_EvalCodeEx ()
from /usr/lib/libpython2.7.so.1.0
#4 0x00007ffff7af83a9 in PyEval_EvalFrameEx ()
from /usr/lib/libpython2.7.so.1.0
#5 0x00007ffff7af91b0 in PyEval_EvalCodeEx ()
from /usr/lib/libpython2.7.so.1.0
#6 0x00007ffff7af83a9 in PyEval_EvalFrameEx ()
from /usr/lib/libpython2.7.so.1.0
#7 0x00007ffff7af91b0 in PyEval_EvalCodeEx ()
from /usr/lib/libpython2.7.so.1.0
#8 0x00007ffff7a88a60 in function_call () from /usr/lib/libpython2.7.so.1.0
#9 0x00007ffff7a64c23 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0
#10 0x00007ffff7a733fd in instancemethod_call ()
from /usr/lib/libpython2.7.so.1.0
#11 0x00007ffff7a64c23 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0
#12 0x00007ffff3c64c7e in ?? ()
from /usr/lib/python2.7/site-packages/PySide/QtCore.so
#13 0x00007ffff3219b7f in ?? () from /usr/lib/libQtCore.so.4
#14 0x00007ffff78060a2 in start_thread () from /usr/lib/libpthread.so.0
---Type to continue, or q to quit---
(gdb) info threads
Id Target Id Frame

• 63 Thread 0x7fff59172700 (LWP 5008) "NotificationThr" 0x00007ffff780cefb in send () from /usr/lib/libpthread.so.0
  17 Thread 0x7fff5a975700 (LWP 4907) "NotificationThr" 0x00007ffff780cd8b in recv () from /usr/lib/libpthread.so.0
  16 Thread 0x7fff5b7fe700 (LWP 4904) "QProcessManager" 0x00007ffff7534fd3 in select () from /usr/lib/libc.so.6
  15 Thread 0x7fff5bfff700 (LWP 4903) "python2" 0x00007ffff780cc7d in accept
  () from /usr/lib/libpthread.so.0
  14 Thread 0x7fff78d05700 (LWP 4902) "python2" 0x00007ffff780cc7d in accept
  () from /usr/lib/libpthread.so.0
  13 Thread 0x7fff63fff700 (LWP 4901) "python2" 0x00007ffff780cc7d in accept
  () from /usr/lib/libpthread.so.0
  12 Thread 0x7fff637fe700 (LWP 4899) "QFileInfoGather" 0x00007ffff780a04f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
  8 Thread 0x7fff79523700 (LWP 4894) "QInotifyFileSys" 0x00007ffff753335d in poll () from /usr/lib/libc.so.6
  7 Thread 0x7fff7a39b700 (LWP 4893) "QFileInfoGather" 0x00007ffff780a04f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
  5 Thread 0x7fff7bb1a700 (LWP 4891) "QThread" 0x00007ffff753335d in poll ()
  from /usr/lib/libc.so.6
  4 Thread 0x7fff7c73a700 (LWP 4890) "python2" 0x00007ffff780a04f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
  ---Type to continue, or q to quit---

[spyder-bot]

From ccordoba12 on 2014-05-16T17:00:33Z

I'm also using PySide (for almost a year) and have not experienced much segfaults (just a couple a month or so).

[spyder-bot]

From contrebasse on 2014-05-19T01:58:18Z

It may be a problem with my local install. If I'm the only one seeing this I don't mind if the bug is closed.

(And I just noticed that my previous comment was in French, sorry.)

[ccordoba12]

Closing because this is a very old issue.