{"action":"created","issue":{"url":"https://api.github.com/repos/oney/react-native-webrtc/issues/92","repository_url":"https://api.github.com/repos/oney/react-native-webrtc","labels_url":"https://api.github.com/repos/oney/react-native-webrtc/issues/92/labels{/name}","comments_url":"https://api.github.com/repos/oney/react-native-webrtc/issues/92/comments","events_url":"https://api.github.com/repos/oney/react-native-webrtc/issues/92/events","html_url":"https://github.com/oney/react-native-webrtc/issues/92","id":160734957,"number":92,"title":"EXC_BAD_ACCESS cricket::ChannelManager::GetSupportedFormats_","user":{"login":"dguillamot","id":12869509,"avatar_url":"https://avatars.githubusercontent.com/u/12869509?v=3","gravatar_id":"","url":"https://api.github.com/users/dguillamot","html_url":"https://github.com/dguillamot","followers_url":"https://api.github.com/users/dguillamot/followers","following_url":"https://api.github.com/users/dguillamot/following{/other_user}","gists_url":"https://api.github.com/users/dguillamot/gists{/gist_id}","starred_url":"https://api.github.com/users/dguillamot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dguillamot/subscriptions","organizations_url":"https://api.github.com/users/dguillamot/orgs","repos_url":"https://api.github.com/users/dguillamot/repos","events_url":"https://api.github.com/users/dguillamot/events{/privacy}","received_events_url":"https://api.github.com/users/dguillamot/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-06-16T18:59:19Z","updated_at":"2016-06-21T05:51:08Z","closed_at":null,"body":"We seem to be getting the following error. Not 100% of the time, but maybe 5-10% ? Have you seen this? Is it in the internal webrtc libraries? Should they be upgraded in react-native-webrtc? Any other thoughts? Thanks!\r\n\r\n\r\nEXC_BAD_ACCESS·Attempted to dereference garbage pointer 0x180.\r\nFull TraceRaw\r\nimmerse:0cricket::ChannelManager::GetSupportedFormats_w(cricket::VideoCapturer*, std::__1::vector<cricket::VideoFormat, std::__1::allocator<cricket::VideoFormat> >*) const\t\r\n immerse:0rtc::Thread::ReceiveSendsFromThread(rtc::Thread const*)\t\r\n immerse:0rtc::MessageQueue::Get(rtc::Message*, int, bool)\t\r\n immerse:0rtc::Thread::ProcessMessages(int)\t\r\n immerse:0rtc::Thread::PreRun(void*)\t\r\n /usr/lib/system/libsystem_pthread.dylib:0_pthread_body\t\r\n/usr/lib/system/libsystem_pthread.dylib:0_pthread_start\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/oney/react-native-webrtc/issues/comments/227346936","html_url":"https://github.com/oney/react-native-webrtc/issues/92#issuecomment-227346936","issue_url":"https://api.github.com/repos/oney/react-native-webrtc/issues/92","id":227346936,"user":{"login":"zxcpoiu","id":5081771,"avatar_url":"https://avatars.githubusercontent.com/u/5081771?v=3","gravatar_id":"","url":"https://api.github.com/users/zxcpoiu","html_url":"https://github.com/zxcpoiu","followers_url":"https://api.github.com/users/zxcpoiu/followers","following_url":"https://api.github.com/users/zxcpoiu/following{/other_user}","gists_url":"https://api.github.com/users/zxcpoiu/gists{/gist_id}","starred_url":"https://api.github.com/users/zxcpoiu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zxcpoiu/subscriptions","organizations_url":"https://api.github.com/users/zxcpoiu/orgs","repos_url":"https://api.github.com/users/zxcpoiu/repos","events_url":"https://api.github.com/users/zxcpoiu/events{/privacy}","received_events_url":"https://api.github.com/users/zxcpoiu/received_events","type":"User","site_admin":false},"created_at":"2016-06-21T05:51:08Z","updated_at":"2016-06-21T05:51:08Z","body":"@dguillamot \r\n\r\nthe issue you post turned out to be a problem on firebase itself, would nothing to do with WebRTC. That issue got a `WontFix` tag.\r\n\r\nI'm not familiar with it, guess that EXC_BAD_ACCESS means someone is trying to access memory blocks which doesn't belonged to him or the pointer has already dereferenced.\r\n\r\nSince react app would mount and unmount components, maybe **one of** the directions to observe is to exam the flow between mount/unmount of the components and start/stop of the WebRTC resources, especially on `RTCView`, ex: WebRTC does not close cleanly before component unmount.\r\n\r\n**two of** the directions is to upgrade WebRTC library to as latest stable as possible which I mentioned in #79\r\n\r\n\r\n"}}
{"actor":{"display_login":"zxcpoiu"}}