Skip to content
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

Error in `python': double free or corruption (!prev) #69

Open
jproman opened this issue Sep 14, 2022 · 2 comments
Open

Error in `python': double free or corruption (!prev) #69

jproman opened this issue Sep 14, 2022 · 2 comments

Comments

@jproman
Copy link

jproman commented Sep 14, 2022

I am writing you because I am trying to use DP5 and I am getting errors at run time.

These are the steps that I am following:

  1. I start the GUI with "python PyDP4_GUI.py"
  2. Add an SD file with two, very similar structures
  3. Add raw NMR data (select my "proton" folder)
  4. Select an output folder
  5. Click on "Clean Structures"
  6. Click on "Solvent" and select DMSO
  7. Click on "Molecular mechanics" and select MacroModel
  8. Click on "DFT Calculations" and select Gaussian. In Advanced Settings I click on "Split Single Poing DFT" and select B3LYP for both the latter and the "NMR Calculations" section
  9. Click on "NMR assignment"
  10. Click on "DP5 Statistics"
  11. Click on "Calculate" button

Right after clicking on the "Calculate" button, the window shuts down and in the console I can see the following error:

QBasicTimer::stop: Failed. Possibly trying to stop from a different thread
QBasicTimer::stop: Failed. Possibly trying to stop from a different thread
qt.qpa.xcb: xcb_shm_detach() failed with error: 128 (Unknown), sequence: 2493, resource id: 56623117, major code: 130 (Unknown), minor code: 2
qt.qpa.xcb: shmdt() failed (22: Invalid argument) for 0x0
*** Error in `python': double free or corruption (!prev): 0x00000000049395f0 ***

Could you provide some advice on how to deal with this error?

Thank you very much

@Jonathan-Goodman
Copy link
Collaborator

This looks like it may be an error with X11. Are you running the calculations and the GUI on the same computer? This previous issue might help:
#49

@jproman
Copy link
Author

jproman commented Sep 20, 2022

Thank you very much for your quick response. We are running the calculations and the GUI on the same computer.

Finally we have decided to switch to the command line and use it there, and it is working fine for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants