stokes-iterative Python demo segfaults when using Trilinos

Bug #1052801 reported by Johannes Ring
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DOLFIN
Fix Released
Medium
Garth Wells

Bug Description

Running the Python version of the stokes-iterative demo results in a segmentation fault when using the Trilinos backend. Changing "amg" to "default" in line 84, that is

  solver = KrylovSolver("tfqmr", "amg")

makes the demo run fine.

The C++ version works fine with "amg".

Related branches

Revision history for this message
Garth Wells (garth-wells) wrote :

Changing the the preconditioner to ilu, the Python version runs fine. It could be related to the order in which objects are destroyed.

Changed in dolfin:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Garth Wells (garth-wells) wrote :

Placing

    del solver

after

    solver.solve(U.vector(), bb)

does not lead to an error. This points to a destruction order issue.

Changed in dolfin:
milestone: none → 1.1.0
Changed in dolfin:
status: Confirmed → In Progress
assignee: nobody → Garth Wells (garth-wells)
Changed in dolfin:
status: In Progress → Fix Committed
Changed in dolfin:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.