{"action":"created","issue":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/611","repository_url":"https://api.github.com/repos/raspberrypi/firmware","labels_url":"https://api.github.com/repos/raspberrypi/firmware/issues/611/labels{/name}","comments_url":"https://api.github.com/repos/raspberrypi/firmware/issues/611/comments","events_url":"https://api.github.com/repos/raspberrypi/firmware/issues/611/events","html_url":"https://github.com/raspberrypi/firmware/issues/611","id":158763381,"number":611,"title":"GPU starts to act up when \"allocs\" reaches ~32800","user":{"login":"loganmc10","id":848146,"avatar_url":"https://avatars.githubusercontent.com/u/848146?v=3","gravatar_id":"","url":"https://api.github.com/users/loganmc10","html_url":"https://github.com/loganmc10","followers_url":"https://api.github.com/users/loganmc10/followers","following_url":"https://api.github.com/users/loganmc10/following{/other_user}","gists_url":"https://api.github.com/users/loganmc10/gists{/gist_id}","starred_url":"https://api.github.com/users/loganmc10/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/loganmc10/subscriptions","organizations_url":"https://api.github.com/users/loganmc10/orgs","repos_url":"https://api.github.com/users/loganmc10/repos","events_url":"https://api.github.com/users/loganmc10/events{/privacy}","received_events_url":"https://api.github.com/users/loganmc10/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-06-06T20:09:27Z","updated_at":"2016-06-06T22:16:52Z","closed_at":null,"body":"I am trying to run an OpenGL ES 2 application (mupen64plus + GlideN64, an N64 emulator).\r\n\r\nYou can see the bug report I filed with them here:\r\n\r\nhttps://github.com/gonetz/GLideN64/issues/1015\r\n\r\nWhen I run \"sudo vcdbg reloc stats\" I can see that every single time the \"allocs\" get to around 32800, the textures start to get messed up, and \"alloc_fails\" starts to climb, with no new \"allocs\" happening.\r\n\r\nAlso, I use raspi2png to grab screenshots and when this happens it stops working with this message: \r\n\"vc_dispmanx_snapshot() failed\".\r\n\r\nIf I close mupen64plus and re-open it, everything starts to work normally again."},"comment":{"url":"https://api.github.com/repos/raspberrypi/firmware/issues/comments/224105760","html_url":"https://github.com/raspberrypi/firmware/issues/611#issuecomment-224105760","issue_url":"https://api.github.com/repos/raspberrypi/firmware/issues/611","id":224105760,"user":{"login":"popcornmix","id":1053730,"avatar_url":"https://avatars.githubusercontent.com/u/1053730?v=3","gravatar_id":"","url":"https://api.github.com/users/popcornmix","html_url":"https://github.com/popcornmix","followers_url":"https://api.github.com/users/popcornmix/followers","following_url":"https://api.github.com/users/popcornmix/following{/other_user}","gists_url":"https://api.github.com/users/popcornmix/gists{/gist_id}","starred_url":"https://api.github.com/users/popcornmix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/popcornmix/subscriptions","organizations_url":"https://api.github.com/users/popcornmix/orgs","repos_url":"https://api.github.com/users/popcornmix/repos","events_url":"https://api.github.com/users/popcornmix/events{/privacy}","received_events_url":"https://api.github.com/users/popcornmix/received_events","type":"User","site_admin":false},"created_at":"2016-06-06T22:16:52Z","updated_at":"2016-06-06T22:16:52Z","body":"I'd suggest:\r\n``vcgencmd cache_flush && sudo vcdbg reloc 2>&1 | grep used | wc -l``\r\nto get the number of allocations. There is no C++ api for this - it is purely a debug feature and not something the arm should have access to.\r\n32K does sound like an awful lot of textures, which I'd suspect was a leak.\r\nPerhaps the developer could identify what a sensible number of textures should be?\r\nPosting the ``vcdbg reloc`` output may confirm if they are definitely textures. The allocated size may give a clue as to what they may contain.\r\nWe could make a test build with, say a 128K limit, but I suspect that will just runs for a bit longer before hitting the limit."}}
{"actor":{"display_login":"popcornmix"}}