![]() ![]() ![]() Tracing has led to one dead-end after another. The crash that is actually happening now, consistently, across all users still experiencing this crash is WebPageProxy::runJavaScriptInMainFrameScriptWorld (see: Webkit Bug 214875), however beyond the stack where the crash is happening, there is no other info to go off of, even the "event" that's triggering it changes between different users or different instances (that was the verbose logging build that was given to some folks a bit ago). I had found this thread on SO quite some time ago and while it was specific to debugging using Xcode and the process being killed by Safari during a debug session, I did try this with one of the test builds (which was unsuccessful). I'm afraid I haven't had a chance to dig around the Bitwarden code enough to know if this is a reasonable solution for it, or where to add the code, but if someone with more context could weigh in, that would be great. Defaultđ1:40:25.204027+0200 runningboarddğinished acquiring assertion 44 (target:xpcservice)ĭefaultđ1:40:25.204255+0200 runningboardd Ignoring resume because this process is not lifecycle managedĭefaultđ1:40:25.204531+0200 runningboardd Set darwin role to: UserInteractiveNonFocalĭefaultđ1:40:25.204801+0200 runningboardd Ignoring GPU update because this process is not GPU managedĭefaultđ1:40:25.281246+0200 distnoted register name: object: token: f426a pid: 81786Įrrorđ1:40:25.375313+0200 tccd Prompting policy for hardened runtime service: kTCCServiceAppleEvents requires entitlement .apple-events but it is missing for ACC:), 1000) to your script.js file to keep some activity going to your extension so it doesn't get killed.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |