{"action":"created","issue":{"url":"https://api.github.com/repos/docker/compose/issues/409","labels_url":"https://api.github.com/repos/docker/compose/issues/409/labels{/name}","comments_url":"https://api.github.com/repos/docker/compose/issues/409/comments","events_url":"https://api.github.com/repos/docker/compose/issues/409/events","html_url":"https://github.com/docker/compose/issues/409","id":40280435,"number":409,"title":"Fig logs produces a MemoryError","user":{"login":"btashton","id":173245,"avatar_url":"https://avatars.githubusercontent.com/u/173245?v=3","gravatar_id":"","url":"https://api.github.com/users/btashton","html_url":"https://github.com/btashton","followers_url":"https://api.github.com/users/btashton/followers","following_url":"https://api.github.com/users/btashton/following{/other_user}","gists_url":"https://api.github.com/users/btashton/gists{/gist_id}","starred_url":"https://api.github.com/users/btashton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/btashton/subscriptions","organizations_url":"https://api.github.com/users/btashton/orgs","repos_url":"https://api.github.com/users/btashton/repos","events_url":"https://api.github.com/users/btashton/events{/privacy}","received_events_url":"https://api.github.com/users/btashton/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/docker/compose/labels/area/logs","name":"area/logs","color":"c7def8"},{"url":"https://api.github.com/repos/docker/compose/labels/kind/bug","name":"kind/bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2014-08-14T17:54:17Z","updated_at":"2015-10-19T21:56:34Z","closed_at":null,"body":"I am consistently getting a MemoryError on containers that produce a lot of logs.\r\n```\r\nfig --version\r\nfig 0.5.2\r\n\r\nfig logs\r\nAttaching to fig_lmsks_1, fig_lmscore_1, fig_lmsweb_1, fig_lmsgw_1\r\nException in thread Thread-3:\r\nTraceback (most recent call last):\r\n  File \"/code/build/fig/out00-PYZ.pyz/threading\", line 810, in __bootstrap_inner\r\n  File \"/code/build/fig/out00-PYZ.pyz/threading\", line 763, in run\r\n  File \"/code/build/fig/out00-PYZ.pyz/fig.cli.multiplexer\", line 41, in _enqueue_output\r\n  File \"/code/build/fig/out00-PYZ.pyz/fig.cli.log_printer\", line 53, in _make_log_generator\r\n  File \"/code/build/fig/out00-PYZ.pyz/fig.cli.utils\", line 100, in split_buffer\r\n  File \"/code/build/fig/out00-PYZ.pyz/fig.packages.docker.client\", line 282, in _multiplexed_socket_stream_helper\r\n  File \"/code/build/fig/out00-PYZ.pyz/fig.packages.docker.client\", line 263, in recvall\r\nMemoryError\r\n```\r\nIf I specify a specific container it usually is fine. "},"comment":{"url":"https://api.github.com/repos/docker/compose/issues/comments/149359543","html_url":"https://github.com/docker/compose/issues/409#issuecomment-149359543","issue_url":"https://api.github.com/repos/docker/compose/issues/409","id":149359543,"user":{"login":"dnephin","id":442180,"avatar_url":"https://avatars.githubusercontent.com/u/442180?v=3","gravatar_id":"","url":"https://api.github.com/users/dnephin","html_url":"https://github.com/dnephin","followers_url":"https://api.github.com/users/dnephin/followers","following_url":"https://api.github.com/users/dnephin/following{/other_user}","gists_url":"https://api.github.com/users/dnephin/gists{/gist_id}","starred_url":"https://api.github.com/users/dnephin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dnephin/subscriptions","organizations_url":"https://api.github.com/users/dnephin/orgs","repos_url":"https://api.github.com/users/dnephin/repos","events_url":"https://api.github.com/users/dnephin/events{/privacy}","received_events_url":"https://api.github.com/users/dnephin/received_events","type":"User","site_admin":false},"created_at":"2015-10-19T21:56:34Z","updated_at":"2015-10-19T21:56:34Z","body":"Sorry, I was saying that the process was probably hitting the `ulimit -m` which imposes a memory limit. Even if the host has plenty of memory, the process may not have access to it.\r\n\r\nThis issue is now really old. Are you still able to reproduce it?  We've only seen two reports of this in a year so I think it's more likely a configuration issue on that system."}}