0001912: Memory management

ID	Project	Category	View Status	Date Submitted	Last Update

0001912	Slicer4	Core: Base Code	public	2012-04-16 23:20	2018-03-02 11:00

Reporter	almar	Assigned To	finetjul
Priority	normal	Severity	tweak	Reproducibility	always
Status	closed	Resolution	won't fix
Product Version	Slicer 4.1.0
Target Version	Slicer 4.7.0	Fixed in Version

Summary	0001912: Memory management
Description	When one is viewing high resolution datasets while using interpolation the RAM is slowly filled up (8 GB in my case). Then a certain threshold is reached (already paging at this stage), Slicer is very slow but speeds up again and viewing the dataset is back to normal. I suspect this has to do with the cache filling up. Is it possible to set a limit to this? So that the RAM cleaning up is done earlier for different RAM configuration? (I have no way to increase my RAM).
Tags	No tags attached.

finetjul 2012-04-17 05:39 administrator ~0004030	It depends what fills up the RAM. It would be necessary to investigate how the memory is used. Depending on what it is, some actions can be done: set the filters in "immediate" processing (no intermediate dataset kept). Before doing that, static and dynamic (valgrind) code analysis must be done to track memory leaks.

almar 2012-04-18 06:02 reporter ~0004040	I have no experience in doing this. I am using the binary slicer as supplied on your website. The problem also seems to occur in general.

finetjul 2012-04-19 05:33 administrator ~0004045	No worries, it was a note for the developer who will take action

lassoan 2017-09-27 13:38 developer ~0015190	I don't see any task that could be worked on in this issue.

Import 2017-06-07 23:51:09: master ad32fd41 2014-08-12 22:32:22 jcfr Details Diff	ENH: Update OpenIGTLink from 1.10.4 to 1.10.10 to include bug fixes. $ git shortlog 3ac5311..849b434 --no-merges Andras Lasso (1): Add the MSG_NOSIGNAL flag to socket send calls to prevent application crash on disconnect on linux systems Gergely Zombori (1): Bug 0001912 - Merged the changes and enhancements from upstream into 'master' Isaiah Norton (1): BUG: use shutdown() instead of close() for sockets Junichi Tokuda (7): BUG: Address issue 0000029: copy igtl_win32hearder.h to the install directory. ENH: Update patch number. STYLE: Update patch number. COMP: Fix compilation error due to lack of MSG_NOSIGNAL option in send() in Mac OS X. For Mac OS X, call setsockopt() with SO_NOSIGPIPE instead. STYLE: Update revision number. BUG: Set timestamp zero, when no timestamp object is registered to image meta message. STYLE: Update patch number Laurent Chauvin (1): BUG: Initialize ImageMessage matrix to identity (issue 0000039) Matt Clarkson (3): 0000044: Put nanosleep in loop to ensure sleep is for the correct time. 0000049: Avoid crash on division by zero, which should never happen 0000050: Convenience methods to set/get igtl_image matrix from 4x4 array of floats z0022myy (1): BUG: Intializing pointer should not be in a loop git-svn-id: http://svn.slicer.org/Slicer4/trunk@23565 3bd1e089-480b-0410-8dfb-8563597acbee
	mod - SuperBuild/External_OpenIGTLink.cmake		Diff File

Date Modified	Username	Field	Change
2012-04-16 23:20	almar	New Issue
2012-04-16 23:20	almar	Status	new => assigned
2012-04-16 23:20	almar	Assigned To	=> finetjul
2012-04-17 05:39	finetjul	Note Added: 0004030
2012-04-18 06:02	almar	Note Added: 0004040
2012-04-19 05:33	finetjul	Note Added: 0004045
2012-08-22 05:56	jcfr	Target Version	=> Slicer 4.3.0
2013-08-09 04:30	finetjul	Target Version	Slicer 4.3.0 => Slicer 4.4.0
2014-05-13 12:48	jcfr	Target Version	Slicer 4.4.0 => Slicer 4.5.0-1
2015-11-02 11:58	jcfr	Target Version	Slicer 4.5.0-1 => Slicer 4.6.0
2016-10-12 03:56	jcfr	Target Version	Slicer 4.6.0 => Slicer 4.7.0
2017-06-10 08:51	jcfr	Changeset attached	=> Slicer master ad32fd41
2017-09-27 13:38	lassoan	Status	assigned => resolved
2017-09-27 13:38	lassoan	Resolution	open => won't fix
2017-09-27 13:38	lassoan	Note Added: 0015190
2018-03-02 11:00	jcfr	Status	resolved => closed