Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Probable memory leak(s) highlighted by live data run #6312

Closed
mantid-builder opened this issue Jun 13, 2012 · 1 comment
Closed

Probable memory leak(s) highlighted by live data run #6312

mantid-builder opened this issue Jun 13, 2012 · 1 comment
Milestone
Release 2.2

Comments

@mantid-builder
Copy link
Collaborator

Original Reporter: Russell Taylor

After running a live data session over a weekend, memory usage was ~25GB even though this was a simple example (and was not preserving events). Check what's going on and fix it.

The run used the FakeEventDataListener to generate 100k events/sec. The class was modified to load in the CNCS instrument. The pre-processing step was a rebin (with PreserveEvents on) and there was no post-processing step. The accumulation method was an add.
@mantid-builder
Copy link
Collaborator Author

This issue was originally trac ticket 5466

@mantid-builder mantid-builder added this to the Release 2.2 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Release 2.2
Development

No branches or pull requests
1 participant
@mantid-builder