(In reply to comment #7, quoting bug 1736312 comment 11) > If the library couldn't be found in memory then the minidump generator will have taken it's ID from the file stored on disk (see [here](https://searchfox.org/mozilla-central/rev/2e3b0483e31abffe0b4374480a34c6d23f5186ea/toolkit/crashreporter/google-breakpad/src/common/mac/macho_id.cc#245-246)). If the loaded library and the one on disk didn't match the resulting minidump will be impossible to symbolicate correctly. Interesting. But I don't see such a mismatch could happen.
Bug 1737201 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to comment #7, quoting bug 1736312 comment 11) > If the library couldn't be found in memory then the minidump generator will have taken it's ID from the file stored on disk (see [here](https://searchfox.org/mozilla-central/rev/2e3b0483e31abffe0b4374480a34c6d23f5186ea/toolkit/crashreporter/google-breakpad/src/common/mac/macho_id.cc#245-246)). If the loaded library and the one on disk didn't match the resulting minidump will be impossible to symbolicate correctly. Interesting. But I don't see how such a mismatch could happen.
(In reply to comment #7, quoting bug 1736312 comment 11) > If the library couldn't be found in memory then the minidump generator will have taken it's ID from the file stored on disk (see [here](https://searchfox.org/mozilla-central/rev/2e3b0483e31abffe0b4374480a34c6d23f5186ea/toolkit/crashreporter/google-breakpad/src/common/mac/macho_id.cc#245-246)). If the loaded library and the one on disk didn't match the resulting minidump will be impossible to symbolicate correctly. Interesting. But I don't see how such a mismatch could happen. Edit: Unless it has something to do with updates.