You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OpenGL visualizer randomly segfaults during live visualization. The backtrace often ends up in the OpenMPI shared objects (on Ubuntu) or the malloc dynamic libraries or the OpenMPI dynamic libraries (macOS).
Reproducible on both Ubuntu 22.04 / Python 3.10.6 / PyOpenGL 3.1.6 and macOS / Python 3.11.2 / PyOpenGL 3.1.6 using this sample from 62d1479:
No ASAN or UBSAN report was generated. The macOS backtrace is almost identical.
Removing the calls to OpenGL.GLUT.glutSolidSphere() in both openGLLive_draw_system_particles() and Sphere.draw() makes fatal errors more difficult to reproduce on Ubuntu and macOS. But then, other sources of fatal errors become visible, such as this backtrace from an Ubuntu release build:
These backtraces almost always feature the ESPResSo custom MpiCallbacks framework, which we are progressively removing from the core in favor of standard MPI communication.
Thanks to Le Qiao for helping investigate the macOS errors.
The text was updated successfully, but these errors were encountered:
The OpenGL visualizer randomly segfaults during live visualization. The backtrace often ends up in the OpenMPI shared objects (on Ubuntu) or the malloc dynamic libraries or the OpenMPI dynamic libraries (macOS).
Reproducible on both Ubuntu 22.04 / Python 3.10.6 / PyOpenGL 3.1.6 and macOS / Python 3.11.2 / PyOpenGL 3.1.6 using this sample from 62d1479:
After a few minutes, the visualizer crashes. Here is a backtrace from a sanitizers build on Ubuntu:
No ASAN or UBSAN report was generated. The macOS backtrace is almost identical.
Removing the calls to
OpenGL.GLUT.glutSolidSphere()
in bothopenGLLive_draw_system_particles()
andSphere.draw()
makes fatal errors more difficult to reproduce on Ubuntu and macOS. But then, other sources of fatal errors become visible, such as this backtrace from an Ubuntu release build:and a very similar one on macOS.
These backtraces almost always feature the ESPResSo custom
MpiCallbacks
framework, which we are progressively removing from the core in favor of standard MPI communication.Thanks to Le Qiao for helping investigate the macOS errors.
The text was updated successfully, but these errors were encountered: