Bug 1513519 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I don't see anything interesting in the reports that have logs on Android. The stack is kinda weird, though.

According to the reports, the crash is occuring in `RefPtr::AddRef()`, so we are likely creating a `RefPtr` with a garbage referent, but frame 1 points to the line[0] where `nsDNSService::AsyncResolveInternal` calls `nsHostResolver::ResolveHost`. We aren't creating a `RefPtr` here, but we would've for the `new nsDNSAsyncRequest(...)` just above for the `mResolver` member. Optimization side effect? Busted stack trace? Also, we're passing the value for `mResolver` from an existing `RefPtr`, so it doesn't make sense that it could suddenly become garbage.

[0] https://searchfox.org/mozilla-central/rev/330daedbeac2bba296d663668e0e0cf248bc6823/netwerk/dns/nsDNSService2.cpp#849

Back to Bug 1513519 Comment 5