Closed msrutek-paylocity closed 2 weeks ago
hi @msrutek-paylocity can you please share the full crash log?
Hi @msrutek-paylocity , can you please share the full crash log?
Hello @MaximShnirman and @orendayan , the full crash log can be found below:
Hi @msrutek-paylocity , From the crash log, I don't see Pendo involved. Why do you think it's related to Pendo?
I'm sorry, that was probably unrelated, however this crash log mentions Pendo.
The question remains the same - Is there anything long-running that might cause the system to perform SIGTERM
?
cc @orendayan @MaximShnirman
Thanks!
Hi @msrutek-paylocity Do you know in which scenario this is happening? You mentioned you are calling trackEvent (Pendo API) when app is entering background but in the stack trace we can see that app has entered foreground. Are you calling trackEvent Pendo API in case of entering foreground also?
Hi @msrutek-paylocity! We've made significant memory management improvements in version 3.4.3 that should help with crashes like this. Please upgrade to 3.4.3 and if you notice similar issues, please open a new ticket with the crash logs. Closing this one.
Platform + Version
iOS 17.5.1 iPhone 15 Pro Max
SDK Version
3.2.2
Framework
Native, SwiftUI
Describe the bug
Hello, since Firebase added support for catching SIGTERM, we started getting thousands of reports of "SIGTERM
__CFRunLoopServiceMachPort
".After examining hundreds of SIGTERM occurrences, many indications point to Pendo. We would like to confirm or deny this theory.
We have code inside
that calls the following Pendo method
Is there anything long-running that might cause the system to perform
SIGTERM
?Thanks!
To Reproduce
Yet unknown.
Expected behavior
No SIGTERM.
Stack Trace