{"action":"created","issue":{"url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/561","labels_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/561/labels{/name}","comments_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/561/comments","events_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/561/events","html_url":"https://github.com/GRIFFINCollaboration/GRSISort/issues/561","id":114102622,"number":561,"title":"Memory leak when producing analysis trees","user":{"login":"jsmallcombe","id":15150313,"avatar_url":"https://avatars.githubusercontent.com/u/15150313?v=3","gravatar_id":"","url":"https://api.github.com/users/jsmallcombe","html_url":"https://github.com/jsmallcombe","followers_url":"https://api.github.com/users/jsmallcombe/followers","following_url":"https://api.github.com/users/jsmallcombe/following{/other_user}","gists_url":"https://api.github.com/users/jsmallcombe/gists{/gist_id}","starred_url":"https://api.github.com/users/jsmallcombe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jsmallcombe/subscriptions","organizations_url":"https://api.github.com/users/jsmallcombe/orgs","repos_url":"https://api.github.com/users/jsmallcombe/repos","events_url":"https://api.github.com/users/jsmallcombe/events{/privacy}","received_events_url":"https://api.github.com/users/jsmallcombe/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-10-29T17:23:34Z","updated_at":"2015-10-30T15:17:38Z","closed_at":null,"body":"This relates to issue to the slow sorting mentioned in #559\r\n\r\nWhen sorting spice data there appears to be a memory leak at the analysis tree construction stage. GRSISort eats up all the memory in even a 32GB machine, goes into swap and hence slows to a crawl.\r\n\r\nWe have had this in all the versions of grsisort and TSiLi we have tried. For several different users and several different computers. By turning off tigress it did seem it might be an issue of event/file rather than the sili class. We aren't sure.\r\n\r\n/tig/midtig02_data/tiguser/SPICETestAnalysis/SPICETestAugust2015/run35661_000.mid\r\n/tig/midtig02_data/tiguser/SPICETestAnalysis/CalibrationFile.cal"},"comment":{"url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/comments/152553348","html_url":"https://github.com/GRIFFINCollaboration/GRSISort/issues/561#issuecomment-152553348","issue_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/561","id":152553348,"user":{"login":"jhenderson88","id":10636847,"avatar_url":"https://avatars.githubusercontent.com/u/10636847?v=3","gravatar_id":"","url":"https://api.github.com/users/jhenderson88","html_url":"https://github.com/jhenderson88","followers_url":"https://api.github.com/users/jhenderson88/followers","following_url":"https://api.github.com/users/jhenderson88/following{/other_user}","gists_url":"https://api.github.com/users/jhenderson88/gists{/gist_id}","starred_url":"https://api.github.com/users/jhenderson88/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhenderson88/subscriptions","organizations_url":"https://api.github.com/users/jhenderson88/orgs","repos_url":"https://api.github.com/users/jhenderson88/repos","events_url":"https://api.github.com/users/jhenderson88/events{/privacy}","received_events_url":"https://api.github.com/users/jhenderson88/received_events","type":"User","site_admin":false},"created_at":"2015-10-30T15:17:38Z","updated_at":"2015-10-30T15:17:38Z","body":"Data files and calibration files for the SPICE data can be found on midtig02 in /data/tiguser/SPICETestAnalysis/\r\n\r\nrun35661_000.mid is what we've been testing on. It is relatively small and yet still fills up the memory when sorting.\r\n\r\nData are being sorted on belodon and midtig02 (my account and James's), the memory issue is seen on both machines."}}