Qtconsole segfaults on OSX when displaying some pop-up function tooltips #1407
Comments
|
Ouch, I was hoping this would be coming from PySide, but you've shown that it can be triggered by PyQt also... First thing to try is to update to the current development tree of IPython, and see if you still get the problem. If that's the case, another question: does the above mechanism always produce the crash, or only some times? |
|
Unfortunately, the problem is still there with the fresh git master clone. And yes, it is very persistent and reliable, the |
|
Thanks for the info, @pshchelo. All I can suggest is that we ask our OSX crew if they've seen the problem as well... @ellisonbg, @minrk, @epatters, can you reproduce this problem by pasting the code @pshchelo posted above? And @pshchelo, in the meantime you can disable tooltips by starting your qtconsole with: or you can put that permanently in your config file if you want. At least it will let you get work done without blowing up in your face, until we can track down this problem. |
|
I am also eager to hear if this is reproducible - I am very new to OSX, and installing all my usual python stuff involved pretty amount of hacking around (as for my taste), so it could be I've just installed/compiled something wrong. |
|
Something tells me it can't be too frequent, or we'd have seen plenty more reports of this problem. If you are new to OSX, you may want to consider using EPD. While it has its own limitations, I've had great success recommending it as a low-pain way for OSX users to get a functioning scientific python stack quickly. But I'm not an OSX user myself, so take anything I say on the platform with a grain of salt :) |
|
This was very reproducible with PySide 1.0.5, but I've never seen it even once since 1.0.7 when the relevant bug was fixed. This could be a new bug in Qt 4.8. |
|
@minrk : I would like to try it with Qt 4.7 if only I could get the corresponding Mac sources for the older PyQt version. It seems that Riverbank does not provide archive of previous releases, at least I could not find any on their website. |
|
I should note that I am also using Qt 4.8 and PySide 1.1.0 from official binaries on OSX 10.7.3, and cannot reproduce this problem. |
|
Right now I tried to uninstall both PyQt and PySide together with Qt, and installed Qt 4.7.4 with PySide 1.1 for this Qt - the problem is gone. But I really suspect I messed up the installation the very first time. I was playing with XCode, installed and reinstalled it couple of times, and now I saw all Qt libs ended up in /Developer-old/ ... Now I will try again uninstall them and install Qt 4.8 versions, since for @minrk it seems to work. |
|
OK, closing then, since it doesn't seem to be on our side. |
|
I am having the same issue as pshchelo. As I'm new to both Python and using package management on the Mac, I followed the installation instructions mentioned here: http://www.thisisthegreenroom.com/2011/installing-python-numpy-scipy-matplotlib-and-ipython-on-lion/#ipython I did not find anything on these instructions regarding PySide, but I was using the Qt 4.8 libraries, and Python 2.7.2 (installed via homebrew), and iPython V 0.12, again installed via pip. Any recommendations? |
|
@venabled: it looks like some quirk in Qt 4.8 and/or the setup process we were using (since @minrk does not have this problem). In the end I installed Qt 4.7.4 and PySide 1.1 for this Qt version from Nokia binary packages and compiled the PyQt 4.9.1 mac-sources against my installed Qt 4.7.4. Now everything works. I use both PySide and PyQt since I learn Qt+Python and want to do it on PySide, but Spyder IDE I use has some annoying troubles with PySide. For IPython/pylab only one of them is enough. |
|
Just an FYI with Qt4.8 this still happens with both PyQt 4.9.1 and with PySide 1.1.0 as the backends. Anytime I try to use sin( or the like I'm out of luck! I think I'm going to try to downgrade to Qt4.7.4 and see if I have any better luck. I'm still not sure how @minrk is doing this without issues? I suppose he mentioned that he was using the apple precompiled binaries? |
|
Ok dropping back to Qt 4.7 and then recompiling PyQt (4.9.1) got it working for me. I had an issue where brew was catching QT as a dependency and installing 4.8, so I needed to pay more attention :D Thanks for talking it over with me! |
|
Is there a clean way to stop brew from catching QT and reinstalling 4.8 or is it best to just skip brew and install PyQt from source? |
|
You can use the "ignore dependencies" flag (just make sure you've satisfied Check out this link for more info: On Fri, Feb 24, 2012 at 5:42 PM, Chris Moore <
|
|
I've got a minimal crashing example : https://gist.github.com/1930794 |
|
I eventually just installed Enthought! |
I am experiencing a very strange behavior of IPython's Qtconsole on MacOSX Lion. The Qtconsole crashes when (from the looks of it) trying to display the function usage tooltip of some functions.
My setup:
MacOSX 10.7.3 (Lion)
Python 2.7.2 (not the system default one, I installed this extra)
IPython 0.12
PyQt 4.9 (installed form official Riverbank sources)
PySide 1.1 for Qt 4.8 for Mac (from official Nokia distribution)
Qt 4.8 (installed libraries only (no SDK) from official Nokia distribution for Mac)
numpy 1.6.1
How to reproduce:
open
ipython qtconsoleand type:What happens:
the tooltip for cos is displayed just fine, but when trying to display the tooltip on
sinusage (after opening the parenthesis) the Qtconsole crashes (segmentation fault) with the report given at the end of this post.I've gone and tested at least the numpy math functions, and there is a pretty large number of such crushing the Qtconsole, namely these are
sin, tan, radians, deg2rad, cosh, round_, rint, expm1, exp2, log10, reciprocal, fmod.I did not tested with any other functions though.
I have tried switching between bindings used by IPython with
QT_APIenvironment variable, checking the active bindings withIPython.external.qt.QT_API. The problem is present in both PyQt4 and PySide version.Note that on Windows (Win7 32-bit Starter) I do not see such bug with the same versions of Python and packages.
Segfault report follows.
The text was updated successfully, but these errors were encountered: