Ticket #4019 (closed: worksforme)
Mantid becomes unresponsive after several hours of use
| Reported by: | Martyn Gigg | Owned by: | Nick Draper |
|---|---|---|---|
| Priority: | critical | Milestone: | Release 2.1 |
| Component: | Mantid | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Stuart Campbell |
Description
I wish to report an issue with Mantid which we've found recently on PEARL at ISIS.
It seems that, after several hours of use, any given instance of Mantid becomes either very slow or, at times, completely unresponsive. The only cure seems to be to try and save the workspace and start a new instance of Mantid.
I've checked with RAL IT that the network drives accessed by Mantid are operating properly and there is no issue with the data analysis PC running the software, which is running Windows 7 with 24 Gb RAM.
Should it be relevant, the version of Mantid installed on PEARL is 1.29.12931 which was released on 30th June 2011.
Many thanks,
Bill Marshall
Change History
comment:1 Changed 9 years ago by Nick Draper
- Priority changed from major to critical
- Status changed from new to assigned
- Owner set to Anyone
comment:2 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 32 to Iteration 33
Moved to iteration 33 at iteration 32 code freeze
comment:3 Changed 9 years ago by Nick Draper
- Owner changed from Anyone to Nick Draper
- Status changed from assigned to accepted
Dropped after the memory improvements in version 2.0
comment:4 Changed 9 years ago by Nick Draper
- Status changed from accepted to verify
- Resolution set to worksforme
