Problem 1827 - exampleB1 crashes at exit if one closes the window with Alt+F4
Summary: exampleB1 crashes at exit if one closes the window with Alt+F4
Status: RESOLVED INVALID
Alias: None
Product: Geant4
Classification: Unclassified
Component: interfaces (show other problems)
Version: 10.2
Hardware: PC Linux
: P5 normal
Assignee: Laurent Garnier
URL:
Depends on:
Blocks:
 
Reported: 2016-02-10 10:17 CET by Olivier Delaune
Modified: 2016-05-03 14:21 CEST (History)
0 users

See Also:


Attachments
segfault backtrace of my own application. (13.19 KB, application/octet-stream)
2016-02-10 10:17 CET, Olivier Delaune
Details

Note You need to log in before you can comment on or make changes to this problem.
Description Olivier Delaune 2016-02-10 10:17:53 CET
Created attachment 383 [details]
segfault backtrace of my own application.

./exampleB1 
Available UI session types: [ Qt, Xm, GAG, tcsh, csh ]
G4WT1 > 
G4WT1 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
G4WT1 >  Local thread RunManagerKernel version Name: geant4-10-02 [MT]
G4WT1 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
G4WT1 > 
G4WT0 > 
G4WT0 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
G4WT0 >  Local thread RunManagerKernel version Name: geant4-10-02 [MT]
G4WT0 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
G4WT0 > 
G4WT1 > ### Adding tracking cuts for neutron  TimeCut(ns)= 10000  KinEnergyCut(MeV)= 0
G4WT0 > ### Adding tracking cuts for neutron  TimeCut(ns)= 10000  KinEnergyCut(MeV)= 0

Graphics systems deleted.
Visualization Manager deleting...
G4WT0 > UserRunAction deleted.
G4WT0 > UserPrimaryGenerator deleted.
G4WT0 > RunManager is deleting RunManagerKernel.
G4WT0 > EventManager deleted.
G4WT0 > Units table cleared.
G4WT0 > Total navigation history collections cleaned: 3
G4WT0 > ================== Deleting memory pools ===================
G4WT0 > Pool ID '20G4NavigationLevelRep', size : 0.00288 MB
G4WT0 > Pool ID '24G4ReferenceCountedHandleIvE', size : 0.000961 MB
G4WT0 > Pool ID '7G4Event', size : 0.000961 MB
G4WT0 > Pool ID '15G4CountedObjectIvE', size : 0.000961 MB
G4WT0 > Number of memory pools allocated: 4; of which, static: 0
G4WT0 > Dynamic pools deleted: 4 / Total memory freed: 0.0058 MB
G4WT0 > ============================================================
G4WT0 > G4Allocator objects are deleted.
G4WT0 > Thread-local UImanager is to be deleted.
G4WT0 > There should not be any thread-local G4cout/G4cerr hereafter.
G4WT1 > UserRunAction deleted.
G4WT1 > UserPrimaryGenerator deleted.
G4WT1 > RunManager is deleting RunManagerKernel.
G4WT1 > EventManager deleted.
G4WT1 > Units table cleared.
G4WT1 > Total navigation history collections cleaned: 3
G4WT1 > ================== Deleting memory pools ===================
G4WT1 > Pool ID '20G4NavigationLevelRep', size : 0.00288 MB
G4WT1 > Pool ID '24G4ReferenceCountedHandleIvE', size : 0.000961 MB
G4WT1 > Pool ID '7G4Event', size : 0.000961 MB
G4WT1 > Pool ID '15G4CountedObjectIvE', size : 0.000961 MB
G4WT1 > Number of memory pools allocated: 4; of which, static: 0
G4WT1 > Dynamic pools deleted: 4 / Total memory freed: 0.0058 MB
G4WT1 > ============================================================
G4WT1 > G4Allocator objects are deleted.
G4WT1 > Thread-local UImanager is to be deleted.
G4WT1 > There should not be any thread-local G4cout/G4cerr hereafter.
G4 kernel has come to Quit state.
UserDetectorConstruction deleted.
UserPhysicsList deleted.
UserActionInitialization deleted.
UserWorkerThreadInitialization deleted.
UserRunAction deleted.
RunManager is deleting RunManagerKernel.
EventManager deleted.
Units table cleared.
Total navigation history collections cleaned: 3
================== Deleting memory pools ===================
Pool ID '20G4NavigationLevelRep', size : 0.00288 MB
Pool ID '24G4ReferenceCountedHandleIvE', size : 0.000961 MB
Pool ID '17G4DynamicParticle', size : 0.000961 MB
Pool ID '15G4CountedObjectIvE', size : 0.000961 MB
Number of memory pools allocated: 4; of which, static: 0
Dynamic pools deleted: 4 / Total memory freed: 0.0058 MB
============================================================
G4Allocator objects are deleted.
UImanager deleted.
StateManager deleted.
RunManagerKernel is deleted. Good bye :)
Erreur de segmentation 

This ends with a segmentation fault if I close the window using Alt+F4 combination. I do not get this segfault if I close the window clicking on the cross in the upper right.
It only happens when one closes the window pressing Alt+F4.

With my own project, I get a backtace that I attached if it could help (once more, I do not get this crash if I click on the cross in the upper right).
I could send you my full project if you need it to debug.
Comment 1 Ivana Hrivnacova 2016-02-10 18:11:10 CET
Thank you for the report.  According to your back trace the problem seems to be in Qt interface. Re-assigning to Laurent Garnier.
Comment 2 Laurent Garnier 2016-02-11 11:55:57 CET
Hi Olivier, 

According to your backtrace, not sure that the problem is from Geant4. 
- No sign of Geant4 in the backtrace
- Yes, there is Qt, but it seems to be called by "Oxygen::Animation::~Animation()"

Could you disable oxygen and retry ?

Laurent
Comment 3 Olivier Delaune 2016-02-15 11:13:30 CET
Hi Laurent, not sure to know how to disable Oxygen. For example I tried to use other window decoration proposed within my Linux distribution but I still get a segmentation fault? The problem is I do not get any backtrace. I will try to install the debug package of these window decoration system to see if I could get a backtrace.
Did you try to reproduce the crash by yourself? Here it is reproducible all the time.
Comment 4 Laurent Garnier 2016-02-15 11:25:20 CET
Hi Olivier

Sorry, I could not reproduce you problem, I do not have a Linux right now.
Did you try to run Geant4 visualisation without Qt (X or Xm) ?

Laurent
Comment 5 Olivier Delaune 2016-02-15 23:29:33 CET
Hi Laurent,
hmmm, I tried these visualisations: X and Xm in addition of Qt and get exactly the same backtrace. I mean the one with some reference to Oxygen.

I also tried to use other window decoration systems and after installing the associated debug packages, I still get the same backtrace. So probably the crash is related to KDE.

I have a CentOs with GNOME 2 on one of my computer so I will try to install GEANT4 10.2 on it to see if the segfault happens on GNOME system.
Comment 6 Laurent Garnier 2016-02-16 13:39:24 CET
Ok, let's see if you still have problems with GNOME2 interface.

Laurent
Comment 7 Olivier Delaune 2016-02-17 10:48:48 CET
Hmmm, I installed GEANT4 10.2 on a CentOs 6.6 64-bits with GNOME 2.28.2.
I also get a segmentation error (core dumped) message.
Unfortunately, I am not able to provide a backtrace since this computer is not connected to Internet and so it is really a mess if I need to install manually all the debug packages.
It is really linked to Qt since I was not able to crash the application if GEANT4 is not compiled with the option -DGEANT4_USE_QT=ON
Comment 8 Laurent Garnier 2016-02-19 15:28:53 CET
Could you do a copy/paste on an usb key of the core dump message ?

Thanks, 
Laurent
Comment 9 Olivier Delaune 2016-02-19 15:34:00 CET
Unfortunately, no it is not possible because there is no core dumped message (except the message that says that there was a core dumped itself).
I have no backtrace because I am not able to install the related debug packages on this Linux.
So basically, what I could provide you is exactly the same as what I wrote in my first message
Comment 10 Olivier Delaune 2016-04-25 16:33:59 CEST
I installed Qt 5.6.0 from sources (using the run file provided by qt.io) and I do not experience anymore this crash. So it is solved with this new Qt version.
Comment 11 Laurent Garnier 2016-05-03 14:21:14 CEST
Ok, thanks for the report.

Cheers, 
Laurent