Now, how come this kind of changes to the Exchange Server passed the QA process since it's affecting a lot of users ?. Almost the same stack trace as others have shown. It'll stay up for maybe a couple of hours, then crash on its own. It crashes even on the background when not interacting with it. I'm also experiencing the problem since this morning. Since I was the one who originally open this thread about a month and a half, I wanted to chime in. That Keychain entry for SfB contains my password.įollowing is an excerpt from the log file:Īnonymous UUID: 39A06E74-4845-F656-DD6C-2F11CCA8C311Ĭrashed Thread: 0 Dispatch queue: -threadĮxception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020 Each time it crashes I also see that in my Keychain 1 entry has a new modified date/time with it being same as when the crash occurred. Path: /Applications/Skype for Business.app/Contents/MacOS/Skype for Business Let me know if the complete crash report is needed. I'm not running any VPN nor there is any other communication problem while accessing any other site on port 443.
From what I can see on the detailed crash report the problem is related to an Secure HTTP (HTTPS) issue since that thread is the one crashing.
Today the latest version of SFB, 16.15.166, started crashing upon starting up.
0 kommentar(er)
