{"action":"created","issue":{"url":"https://api.github.com/repos/JuliaLang/julia/issues/14112","labels_url":"https://api.github.com/repos/JuliaLang/julia/issues/14112/labels{/name}","comments_url":"https://api.github.com/repos/JuliaLang/julia/issues/14112/comments","events_url":"https://api.github.com/repos/JuliaLang/julia/issues/14112/events","html_url":"https://github.com/JuliaLang/julia/issues/14112","id":118498543,"number":14112,"title":"Hitting some memory limit well below physical limit?","user":{"login":"sbromberger","id":941359,"avatar_url":"https://avatars.githubusercontent.com/u/941359?v=3","gravatar_id":"","url":"https://api.github.com/users/sbromberger","html_url":"https://github.com/sbromberger","followers_url":"https://api.github.com/users/sbromberger/followers","following_url":"https://api.github.com/users/sbromberger/following{/other_user}","gists_url":"https://api.github.com/users/sbromberger/gists{/gist_id}","starred_url":"https://api.github.com/users/sbromberger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sbromberger/subscriptions","organizations_url":"https://api.github.com/users/sbromberger/orgs","repos_url":"https://api.github.com/users/sbromberger/repos","events_url":"https://api.github.com/users/sbromberger/events{/privacy}","received_events_url":"https://api.github.com/users/sbromberger/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":18,"created_at":"2015-11-23T23:32:16Z","updated_at":"2015-11-25T21:00:55Z","closed_at":"2015-11-25T13:47:49Z","body":"I'm not sure whether this is a Julia thing or an OS thing, but here's what happened.\r\n\r\nI'm on a machine with 512 GB of RAM (yes, GB) and `Version 0.4.2-pre+15 (2015-11-20 12:12 UTC)`:\r\n\r\n```\r\njulia> using LightGraphs\r\n\r\njulia> @time g = Graph(1_000_000_000, 10_000_000_000)\r\nincrease REGION_COUNT or allocate less memory\r\n\r\nsignal (6): Aborted\r\ngsignal at /lib64/libc.so.6 (unknown line)\r\nabort at /lib64/libc.so.6 (unknown line)\r\nmalloc_page at /g/g17/seth/dev/julia/julia/src/gc.c:701\r\nadd_page at /g/g17/seth/dev/julia/julia/src/gc.c:1031\r\n__pool_alloc at /g/g17/seth/dev/julia/julia/src/gc.c:1073\r\narray_resize_buffer at /g/g17/seth/dev/julia/julia/src/array.c:594\r\npush! at ./array.jl:434\r\nunsafe_add_edge! at /g/g17/seth/.julia/v0.4/LightGraphs/src/graph.jl:80\r\nadd_edge! at /g/g17/seth/.julia/v0.4/LightGraphs/src/core.jl:108\r\nAborted (core dumped)\r\n\r\n```\r\nAt last check the memory allocation for the process was approaching 100 GB.\r\n\r\nAny ideas? I don't know what `REGION_COUNT` is. Looks like it's defined here: https://github.com/JuliaLang/julia/blob/master/src/gc.c#L745-L747"},"comment":{"url":"https://api.github.com/repos/JuliaLang/julia/issues/comments/159730554","html_url":"https://github.com/JuliaLang/julia/issues/14112#issuecomment-159730554","issue_url":"https://api.github.com/repos/JuliaLang/julia/issues/14112","id":159730554,"user":{"login":"sbromberger","id":941359,"avatar_url":"https://avatars.githubusercontent.com/u/941359?v=3","gravatar_id":"","url":"https://api.github.com/users/sbromberger","html_url":"https://github.com/sbromberger","followers_url":"https://api.github.com/users/sbromberger/followers","following_url":"https://api.github.com/users/sbromberger/following{/other_user}","gists_url":"https://api.github.com/users/sbromberger/gists{/gist_id}","starred_url":"https://api.github.com/users/sbromberger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sbromberger/subscriptions","organizations_url":"https://api.github.com/users/sbromberger/orgs","repos_url":"https://api.github.com/users/sbromberger/repos","events_url":"https://api.github.com/users/sbromberger/events{/privacy}","received_events_url":"https://api.github.com/users/sbromberger/received_events","type":"User","site_admin":false},"created_at":"2015-11-25T21:00:55Z","updated_at":"2015-11-25T21:00:55Z","body":"Also, is there merit in suggesting some function (like a reverse \"sizehint!\") that will deallocate memory when the user is satisfied that the structure won't grow significantly (and when s/he is prepared to deal with an inefficiency if it does need to grow)?"}}