Apparent memory leak during output diagrams in Pop!_OS: MG5 v3.4.1
I am running MG5 v3.4.1 on Pop!_os linux distribution. When I try to generate diagrams for any simple process, MG5 hangs when I try output <foldername>;
$ ./MG5_aMC_
...
[sm model loaded]
...
MG5_aMC>generate e+ e- > e+ e-
INFO: Checking for minimal orders which gives processes.
INFO: Please specify coupling orders to bypass this step.
INFO: Trying process: e+ e- > e+ e- WEIGHTED<=4 @1
INFO: Process has 4 diagrams
1 processes with 4 diagrams generated in 0.004 s
Total: 1 processes with 4 diagrams
MG5_aMC>output test
I notice rampant memory usage in the system monitor at this last step until the computer freezes. I'm not sure if this is a Pop!_os issue or an MG5 issue, but I cannot replicate the issue in MG5 v2.9.13.
However, in v3.4.1 if I instead just use 'output' with no specified folder name, things proceed smoothly;
MG5_aMC>output
INFO: initialize a new directory: PROC_sm_0
INFO: remove old information in PROC_sm_0
INFO: Organizing processes into subprocess groups
INFO: Generating Helas calls for process: e+ e- > e+ e- WEIGHTED<=4 @1
INFO: Processing color information for process: e+ e- > e+ e- @1
INFO: Creating files in directory P1_ll_ll
INFO: Some T-channel width have been set to zero [new since 2.8.0]
if you want to keep this width please set "zerowidth_
INFO: Generating Feynman diagrams for Process: e+ e- > e+ e- WEIGHTED<=4 @1
INFO: Finding symmetric diagrams for subprocess group ll_ll
Generated helas calls for 1 subprocesses (4 diagrams) in 0.004 s
Wrote files for 12 helas calls in 0.024 s
ALOHA: aloha starts to compute helicity amplitudes
ALOHA: aloha creates 3 routines in 0.631 s
save configuration file to /home/thompson/
INFO: Use Fortran compiler gfortran
INFO: Use c++ compiler g++
INFO: Generate jpeg diagrams
INFO: Generate web pages
Output to directory /home/thompson/
Type "launch" to generate events from this process, or see
/home/thompson/
Run "open index.html" to see more information about this process.
MG5_aMC>
Any idea what the issue could be? Would love some help to debug! In the meantime, I will use 2.9.13 for now which seems to work fine.
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Olivier Mattelaer
- Solved:
- Last query:
- Last reply: