{"action":"created","issue":{"url":"https://api.github.com/repos/JuliaLang/julia/issues/15467","repository_url":"https://api.github.com/repos/JuliaLang/julia","labels_url":"https://api.github.com/repos/JuliaLang/julia/issues/15467/labels{/name}","comments_url":"https://api.github.com/repos/JuliaLang/julia/issues/15467/comments","events_url":"https://api.github.com/repos/JuliaLang/julia/issues/15467/events","html_url":"https://github.com/JuliaLang/julia/issues/15467","id":140318783,"number":15467,"title":"Possible memory leak for parallel processing in 0.4.3","user":{"login":"CodeLenz","id":3483767,"avatar_url":"https://avatars.githubusercontent.com/u/3483767?v=3","gravatar_id":"","url":"https://api.github.com/users/CodeLenz","html_url":"https://github.com/CodeLenz","followers_url":"https://api.github.com/users/CodeLenz/followers","following_url":"https://api.github.com/users/CodeLenz/following{/other_user}","gists_url":"https://api.github.com/users/CodeLenz/gists{/gist_id}","starred_url":"https://api.github.com/users/CodeLenz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CodeLenz/subscriptions","organizations_url":"https://api.github.com/users/CodeLenz/orgs","repos_url":"https://api.github.com/users/CodeLenz/repos","events_url":"https://api.github.com/users/CodeLenz/events{/privacy}","received_events_url":"https://api.github.com/users/CodeLenz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-03-11T23:37:35Z","updated_at":"2016-03-14T12:03:57Z","closed_at":null,"body":"I have a large codebase that runs without any problems in 0.4.0, but  shows symptoms of memory leak when running in 0.4.3. \r\n\r\nBasically, the memory increases after a call to @sync @parallel for. It seems that some of the memory allocated for the parallel processing is not freed. A call to gc() in the end of the loop does not fixes the problem.\r\n\r\nThe figure below shows the memory allocation for the same script using 0.4.0 (first half of the graphic) and 0.4.3, where it can be seen thtat the memory increases after each calling @sync @parallel for.\r\n\r\n![processos](https://cloud.githubusercontent.com/assets/3483767/13718421/8878a058-e7c8-11e5-815e-51443282bcbc.png)\r\n\r\nIt is the first time a fill an issue, so if I am not using the proper words/methodology, I apologize. "},"comment":{"url":"https://api.github.com/repos/JuliaLang/julia/issues/comments/196279583","html_url":"https://github.com/JuliaLang/julia/issues/15467#issuecomment-196279583","issue_url":"https://api.github.com/repos/JuliaLang/julia/issues/15467","id":196279583,"user":{"login":"amitmurthy","id":117461,"avatar_url":"https://avatars.githubusercontent.com/u/117461?v=3","gravatar_id":"","url":"https://api.github.com/users/amitmurthy","html_url":"https://github.com/amitmurthy","followers_url":"https://api.github.com/users/amitmurthy/followers","following_url":"https://api.github.com/users/amitmurthy/following{/other_user}","gists_url":"https://api.github.com/users/amitmurthy/gists{/gist_id}","starred_url":"https://api.github.com/users/amitmurthy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amitmurthy/subscriptions","organizations_url":"https://api.github.com/users/amitmurthy/orgs","repos_url":"https://api.github.com/users/amitmurthy/repos","events_url":"https://api.github.com/users/amitmurthy/events{/privacy}","received_events_url":"https://api.github.com/users/amitmurthy/received_events","type":"User","site_admin":false},"created_at":"2016-03-14T12:03:57Z","updated_at":"2016-03-14T12:03:57Z","body":"I just tested with the above code on \r\n```\r\nJulia Version 0.4.4-pre+43\r\nCommit 147d6d0* (2016-03-07 00:34 UTC)\r\nPlatform Info:\r\n  System: Darwin (x86_64-apple-darwin14.5.0)\r\n```\r\n\r\nAfter all iterations finished I required 2 executions of `@everywhere gc()` to release all memory. There is no leak. This is the same issue as https://github.com/JuliaLang/julia/issues/15415, the generational gc is holding onto objects a bit longer.\r\n\r\n@carnaval , @yuyichao , if we could specify the maximum heap size (like Java's -Xmx startup argument), the user can better control how much a Julia process is allowed to grow."}}