Open lucafedeli88 opened 2 years ago
cc @kngott could that be related to what you saw with graphs this week?
Hello ! I have investigated a little bit this issue. It seems to me that what happens is the following:
1) when the moving window is activated, shiftMF
is called on all the multifabs
2) shiftMF
also acts on costs (I am using timers - based load-balancing)
3) in this specific example the simulation is partitioned into 8 boxes, so most multifabs and the costs array have a size equal to 8
4) we have an issue when we call shiftMF
on pml_B
, since pml_B
in this particular example has a size equal to 24, and indices from 0 to 23 are used to access also the components of costs (which has a size equal to 8 ). Do you have an idea about how to fix the issue ? Should we add more components to costs ? should we disable costs update if a multifab is a PML ? should we do something else ?
I am opening this issue because I have observed an invalid memory access when moving window and load-balancing based on timers are used in combination.
Here I provide a small reproducer:
When WarpX runs this inputfile (even without GPUs or OMP support),
valgrind
detects the following issue: