You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't seem to find a pattern, but I intermittently get a stack corruption error that crashes my node process with a SIGABRT. I went into the console and found the following backtrace:
It looks like it's happening in the Peripheral::GetManufacturerData method. I tried to add logging to see if anything would come out at the beginning of the method before the stack corruption occurs, but nothing was logging. I also tried updating SimpleBLE since the backtrace mentions simpleble.node to 0.9.0 and 0.8.1 but the behavior remains.
Relevant version info:
webbluetooth: 3.2.1
MacOS: 14.5
Edit: Other relevant information: I'm attempting to connect to several devices simultaneously which I've noticed can trigger other issues elsewhere in the library. Potentially a race condition of some sort or maybe multiple devices clobbers values in the stack for some reason?
The text was updated successfully, but these errors were encountered:
I can't seem to find a pattern, but I intermittently get a stack corruption error that crashes my node process with a SIGABRT. I went into the console and found the following backtrace:
It looks like it's happening in the Peripheral::GetManufacturerData method. I tried to add logging to see if anything would come out at the beginning of the method before the stack corruption occurs, but nothing was logging. I also tried updating SimpleBLE since the backtrace mentions
simpleble.node
to 0.9.0 and 0.8.1 but the behavior remains.Relevant version info:
webbluetooth: 3.2.1
MacOS: 14.5
Edit: Other relevant information: I'm attempting to connect to several devices simultaneously which I've noticed can trigger other issues elsewhere in the library. Potentially a race condition of some sort or maybe multiple devices clobbers values in the stack for some reason?
The text was updated successfully, but these errors were encountered: