Ticket #7542 (closed: worksforme)
Hard to find memory issue
| Reported by: | Owen Arnold | Owned by: | Nick Draper |
|---|---|---|---|
| Priority: | critical | Milestone: | Release 3.0 |
| Component: | Framework | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Nick Draper |
Description
There appears to be a hard-to-find memory leak somewhere in the ISIS SXD workflow on RHEL6. This issue could be coming from UI components, as well as possibly from Workspaces, Algorithms. These seems to be non-reproducible by the user, but annoying enough for them to request that we fix them. What do we do?
We could test algorithmic aspects of the workflow using VALGRIND, but that won't guarantee that we catch issues in the UI's. It would possibly route out the algorithms as a cause of the issues.
We need a strategy for how to track down this issue.
Change History
comment:2 Changed 7 years ago by Nick Draper
Meeting booked for the 21st of August to get people's heads together.
comment:3 Changed 7 years ago by Nick Draper
- Status changed from new to verify
- type changed from enhancement to task
- Resolution set to worksforme
Held a brainstorming session, we need to see how the items discussed help people as time goes on or if we need better tools.
Get peoples heads together on this one.