Privateer eats up all memory and segfaults when processing PETSc
Bug #366337 reported by
Gregory Crosswhite
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Privateer |
Fix Committed
|
Medium
|
Gregory Crosswhite | ||
Bug Description
When running Privateer on PETSc, it consumes an amount of memory that progressively increases as it makes its way through Pass 1, and eventually results in a segfault.
Related branches
Revision history for this message
| Gregory Crosswhite (gcrosswhite) wrote | #1 |
| Changed in privateer: | |
| assignee: | nobody → gcrosswhite |
| importance: | Undecided → Medium |
| milestone: | none → 0.3 |
| status: | New → Confirmed |
Revision history for this message
| Gregory Crosswhite (gcrosswhite) wrote | #2 |
| Changed in privateer: | |
| status: | Confirmed → Fix Committed |
To post a comment you must log in.
I suspect that this might be a problem with Haskell's laziness... will try modifying the code to strictly evaluate global variables to see if that works.