{"action":"created","issue":{"url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/457","labels_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/457/labels{/name}","comments_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/457/comments","events_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/457/events","html_url":"https://github.com/GRIFFINCollaboration/GRSISort/issues/457","id":103403038,"number":457,"title":"Memory leak in analysis tree construction (TIGRESS)","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},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":23,"created_at":"2015-08-27T01:43:52Z","updated_at":"2015-09-08T14:40:33Z","closed_at":null,"body":"There appears to be a memory leak somewhere in the analysis tree construction for TIGRESS data. The RAM usage just increases constantly throughout the analysis tree building process (eventually maxing out the RAM on midtig02). This is with the latest version pulled as of a few hours ago.\r\n\r\nI asked @SmithJK and was told similar things were not seen with the recent versions and GRIFFIN data, so it might be a TIGRESS exclusive issue.\r\n\r\nI ran valgrind, the (more significant) outputs of which can be found on the ELog (elog.triumf.ca/Tigress/TIGRESS/12948).\r\n\r\nThis was all done on the Tiguser account, with the trees of interest in the SPICETestAnalysis directory.\r\n\r\nOn a perhaps related note: We have recently started receiving _M_range_check terminations with TIGRESS data, seemingly associated with Fragments containing zero-length Charge vectors. This was solved trivially by the inclusion of a Charge.size()>0 requirement locally."},"comment":{"url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/comments/138587047","html_url":"https://github.com/GRIFFINCollaboration/GRSISort/issues/457#issuecomment-138587047","issue_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/457","id":138587047,"user":{"login":"r3dunlop","id":5428160,"avatar_url":"https://avatars.githubusercontent.com/u/5428160?v=3","gravatar_id":"","url":"https://api.github.com/users/r3dunlop","html_url":"https://github.com/r3dunlop","followers_url":"https://api.github.com/users/r3dunlop/followers","following_url":"https://api.github.com/users/r3dunlop/following{/other_user}","gists_url":"https://api.github.com/users/r3dunlop/gists{/gist_id}","starred_url":"https://api.github.com/users/r3dunlop/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/r3dunlop/subscriptions","organizations_url":"https://api.github.com/users/r3dunlop/orgs","repos_url":"https://api.github.com/users/r3dunlop/repos","events_url":"https://api.github.com/users/r3dunlop/events{/privacy}","received_events_url":"https://api.github.com/users/r3dunlop/received_events","type":"User","site_admin":false},"created_at":"2015-09-08T14:40:33Z","updated_at":"2015-09-08T14:40:33Z","body":"@jhenderson88, how large are the output files that are being written?"}}