| Summary: | Segfault in QT5 on exit from example B1 | ||
|---|---|---|---|
| Product: | Geant4 | Reporter: | Pavel Reznicek <pavel.reznicek> |
| Component: | visualization | Assignee: | John.Allison |
| Status: | VERIFIED LATER | ||
| Severity: | minor | CC: | stephan.lachnit |
| Priority: | P4 | ||
| Version: | 10.7 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
|
Description
Pavel Reznicek
2020-08-14 14:11:29 CEST
Hi Pavel Does this issue remain? I was hoping that someone using Debian would confirm this problem and provide more information. I am not in a position to test on Debian. On my platform (Mac) all's OK. The issue, as you say, is harmless. On the assumption that this issue will go away with newer versions of Geant4, Qt and Debian, I propose closing this bug report. John Dear John, the issue still remains. It may be well bug in QT (v5.14.2). as well as in the way Geant4 calls the QT functions (e.g. too new version of QT?). If you would see any more info I could provide, I would be happy to. Otherwise waiting for new QT/Debian/Geant4 version is indeed the only thing we can do now. Best regards, Pavel I have in problem as well, and for every Geant4 UI program. I suspect that something is improperly deleted (or not deleted, kinda depends). It is pretty harmless as it will only occur when closing the application and only in Gui mode. Also running Debian Sid. Just for the record: the problem still persists even with updated QT version (5.15.2) and Geant4 version (10.7.p01). Would I be right in saying this seems to be a Debian issue? Well, there is no such problem in Debian stable (QT v5.11). So I would guess it is a problem of Geant4 compatibility with new QT version > ~5.14. I tried also CERN lxplus, but it has also old QT (v5.12). Test on latest Fedora could tell more, but I don't have access to such a machine. PS: It may also be a combination of the latest QT with the fact that my Geant4 is compiled with multithreading enabled. But it is a guess. Hi Pavel > Just for the record: the problem still persists even with updated QT version (5.15.2) and Geant4 version (10.7.p01). > PS: It may also be a combination of the latest QT with the fact that my Geant4 is compiled with multithreading enabled. But it is a guess. Just to say...I'm on MacOS with Qt 5.15.0 and G4 10.7+ and all's OK. > Most likely it is harmless (happens in derstructor of the QT viewer), but still would be good to resolve. I don't think we have any Qt experts using Debian, so let's close this for now. Sorry. John OK. Let's close that. PS: just found out it has been discussed also here: https://geant4-forum.web.cern.ch/t/qt5-opengl-segmentation-fault/3319/9, without resolution though... Please don't close this just because there is no one able to fix it. This has just occurred to me... How are you exiting your app? I too find a segfault (below) if I hit the window delete button but if I exit "cleanly" by typing "exit" in the command line window all is well. Thread 1: EXC_BAD_ACCESS (code=1, address=0x8) #0 0x00000001039c9477 in QOpenGLContext::makeCurrent(QSurface*) () #1 0x0000000102be0af4 in QGLContext::makeCurrent() () #2 0x0000000102be13f7 in QGLWidget::makeCurrent() () #3 0x0000000100aa0d7d in G4OpenGLStoredQtViewer::~G4OpenGLStoredQtViewer() at /Users/johna/Geant4/geant4-dev/source/visualization/OpenGL/src/G4OpenGLStoredQtViewer.cc:68 Ah, I can confirm this, when I exit by typing the command, I don't get a segfault as well. OK. Progress. This is a long-standing issue. Even for plain X or Xm windows, hitting the delete button causes problems. We need to fix this (but it won't be top priority :-) |