Microsoft Word: Stream 0x84f7fbf0 is sending an event before being opened We'd need more concrete steps to reproduce the problem, and possibly even a document that triggers the behavior for you. While not a guaranteed issue it did give us enough information to work with Apple to identify the problem, and then we had to wait for Apple to finalize the 10.11.1 update and release it.Īs for background grammar checking never finishing, I'm not aware of an issue like that. As of one of the last few El Capitan betas, the reports of this problem spiked, but at our best we could only force a reproducible case about one time in three here at work. We were aware of a spike in these events but the problem was intermittent and actually appeared to go away in some of the middle betas of El Capitan, probably due to random memory being filled out differently and avoiding the data misinterpretation in the OS. To the user, though, it looks identical to any other time the apps crash and we put up the MERP crash reporter UI. Our crash reporter then dutifully reports the crash back to us, and due to the particular fingerprint in the crash report we know it was really a hang, not a crash. Our hang detection code runs on a background thread and when it notices that the main thread hasn't budged in a while (I forget what the threshold is), it forces a crash with a particular fingerprint.
My main issue with Word right now is background grammar checking that never finishes (US English).Ĭoncretely, the sqlite bug would cause the Office 2016 apps to hang (usually on boot).
But what kind of issue did it cause, concretely?
0 kommentar(er)
