STACK TRACE unable to capture data

[fengzhonglingluandeduanfa]

STACK TRACE unable to capture data

[luke-belton]

Hi @fengzhonglingluandeduanfa - please could you write into [email protected] quoting this GitHub issue, with a link to the event in your Bugsnag dashboard. We'd be happy to investigate more from there 👍

[fengzhonglingluandeduanfa]

Is this the link you need?
https://app.bugsnag.com/dong-wan-xin-ke-ji-zhu-yan-jiu-kai-fa-you-xian-gong-si/comchat-ios/errors/62c3a5ce577210000ae6a551?filters[event.since]=30d&filters[error.status]=open&event_id=62d0caa80095457b6db20000

[luke-belton]

Hi @fengzhonglingluandeduanfa - the error you've shared a link to is an Out of Memory error. These can't be detected directly in Bugsnag, so we use a heuristic, by monitoring for the app closing unexpectedly and inferring that it's an Out of Memory error by ruling out other known app termination causes.

We're only able to detect these when the app is relaunched, at which time there is limited data available, including no stacktrace. As a result we display the unknown file unknown method placeholder in the dashboard.

This has also been discussed on other issues previously, e.g. at #1145 (comment). I'm going to close this out for now, but feel free to write into [email protected] if you have further questions on this subject.