-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bizarre invalid selection / selection just gives up #336
Comments
I am observing this too. |
It's not just me! For reference this issue has never gone away, it just comes and goes sometimes. |
@EvanKomp Are you also observing this only on Mac? |
In my case, I have an object named |
I'm using Fedora 39 with Python 3.10.16 and PyMOL 3.1.3. |
Hi,
I'm been using pymol for a long time, using original PyMOL 1 and PyMOL 2 on El Capitan. I recently had to update my mac to Monterey, and now, pymol crashes in bizarre ways.
Here's a minimal test snippet that will crash for me (regardless of what protein is displayed (even none)):
Notably, this doesn't crash on i == 0. It crashes on i == 11.
This snippet crashes in the gui (whether you 1-line it for the command prompt or put it in a script and call run) in both open source and closed source versions. I've tried both 2.5.7 and 2.5.8.
Once you get into this state. There's a broken selection called "test" that displays in the gui (and displays in cmd.get_names()), but clearly is broken because pymol throws an error when you click on the "A" button.
I do not get this crash or the glitchy selection when running these snippets from the commandline (using ipython and import pymol). It also does not crash when running in my .pymolrc and launching the gui.
Debugging
This snippet does not crash:
Then, it gets weirder. If you run that bad line multiple times, you have to fix it multiple times.
Here's a table with the minimum values of B I could get this to NOT crash at for a given value of A. These values are the same in both the closed and open source versions.
But once you call that command 15 times, it just works. (i.e. if A is >= 15, B can be 0)
Anyways, I'm happy to help get this bug fixed. Or, please just tell me how to remove all traces of pymol from my computer so I can reinstall. I've tested with some other people and these bugs don't exist. I don't know what's wrong with my install.
The text was updated successfully, but these errors were encountered: