Re: [deal.II] Re: Internal instability of the GMRES Solver / Trilinos

2017-03-16 Thread Martin Kronbichler
Dear Pascal, No, you do not need to try the other solution. I'm glad I could help. (This asserts the approach that we need to be careful with the vector pool between different calls.) Best, Martin On 16.03.2017 15:21, Pascal Kraft wrote: > Hi Martin, > > I have tried a version > with >

Re: [deal.II] Re: Internal instability of the GMRES Solver / Trilinos

2017-03-16 Thread Pascal Kraft
Dear Martin, my local machine is dying to a Valgrind run at the moment, but as soon as that is done with one step I will put these changes in right away and post the results here (<6 hrs). >From what I make of the call stacks on process somehow gets out of the SameAs() call without being

Re: [deal.II] Re: Internal instability of the GMRES Solver / Trilinos

2017-03-15 Thread Martin Kronbichler
Dear Pascal, This problem seems related to a problem we recently worked around in https://github.com/dealii/dealii/pull/4043 Can you check what happens if you call GrowingVectorMemory::release_unused_memory() between your optimization steps? If a communicator gets stack in those places it

[deal.II] Re: Internal instability of the GMRES Solver / Trilinos

2017-03-15 Thread Pascal Kraft
Dear Timo, I have done some more digging and found out the following. The problems seem to happen in trilinos_vector.cc between the lines 240 and 270. What I see on the call stacks is, that one process reaches line 261 ( ierr = vector->GlobalAssemble (last_action); ) and then waits inside this