Open PTR-inc opened 2 years ago
And some extra log, maybe unrelated and on older mesh/agent versions, just for completeness:
[2021-07-20 12:18:54 AM] Microstack STUCK: @ [FuncAddr: 0x97A94D0BF77F0000] [FuncAddr: 0x8C524D0BF77F0000] [FuncAddr: 0x4AE8480BF77F0000] [FuncAddr: 0x6B99470BF77F0000] [FuncAddr: 0x435C480BF77F0000] [FuncAddr: 0x7815480BF77F0000] [FuncAddr: 0x5299470BF77F0000] [FuncAddr: 0x2693450BF77F0000] [FuncAddr: 0xC09C470BF77F0000] [FuncAddr: 0xA993450BF77F0000] [FuncAddr: 0x23B74B0BF77F0000] [FuncAddr: 0xF0A94D0BF77F0000] [FuncAddr: 0x70754D0BF77F0000] [FuncAddr: 0x92C4440BF77F0000] [FuncAddr: 0xA8174F0BF77F0000] [StartServiceW] [BaseThreadInitThunk] [RtlUserThreadStart]
[2021-09-11 05:28:21 AM] [410386E169589265] ..\microstack\ILibParsers.c:3123 (0,0) Microstack STUCK: @ [FuncAddr: 0x29717370F67F0000] [FuncAddr: 0x8EE07370F67F0000] [FuncAddr: 0xF4E27370F67F0000] [FuncAddr: 0x3BDC7370F67F0000] [FuncAddr: 0xD0646A70F67F0000] [FuncAddr: 0x04537470F67F0000] [FuncAddr: 0x2D547470F67F0000] [FuncAddr: 0x6B357370F67F0000] [FuncAddr: 0x7E407370F67F0000] [FuncAddr: 0x32A87370F67F0000] [FuncAddr: 0xADC46A70F67F0000] [FuncAddr: 0x884B7570F67F0000] [StartServiceW] [BaseThreadInitThunk] [RtlUserThreadStart]
[2022-03-27 10:18:43 AM] [C0A2CB8FEFAA7414] ..\microstack\ILibParsers.c:2717 (0,0) FATAL EXCEPTION @ [FuncAddr: 0x00007ff67fa4e5ac / BaseAddr: 0x00007ff67faca6ec / Delta: 508224]
Hi All,
We are seeing the same thing on one of our connected endpoints. Although it is a Windows 10 laptop.
I did fix an edge case bug I found that caused a 100% cpu spike. That will be included in the upcoming agent update. Hopefully this is related to your issue.
Awesome... once it's applied, we'll keep an eye out and let you know if we see it again.
Since this is still open, I'll chime in that this still seems to be an issue with the Dec 2022 agent. I opened an issue on the agent repository, but that issue tracker seems relatively dead, so bumping this. https://github.com/Ylianst/MeshAgent/issues/194
issue tracker seems relatively dead
They're all moderately dead...unless you're going to fix it youself, or hire someone to fix it for you.
Describe the bug The windows meshagent sometimes hangs/100% cpu. Connection to server is lost. A service restart doesn't work, service not responding. Have to kill the meshagent.exe (there is only one process). Could take over a hanging meshagent pc through rdp and ran prcomon to see what it was trying to do, but no procmon logging at all for the meshagent process.
Log from the agent: [2022-08-03 04:18:44 PM] [47A927806EDB6DFA] ..\microstack\ILibParsers.c:2773 (0,0) FATAL EXCEPTION @ [FuncAddr: 0x000001b951faeaa8 / BaseAddr: 0x00007ff69c7eb298 / Delta: 138801708255216]
To Reproduce Happens intermittently
Expected behavior No hangs
Server Software (please complete the following information):
Client Device (please complete the following information):
Remote Device (please complete the following information):