-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
Describe the bug
I encountered a significant crash while using Starscream in my test app, and the specific stack trace is as follows:
Thread 51 Crashed:
0 libobjc.A.dylib objc_msgSend + 32
1 myapp FoundationStream.write(data:) (WebSocket.swift:242)
2 myapp protocol witness for WSStream.write(data:) in conformance FoundationStream (:0)
3 myapp $s12Starscream9WebSocketC12dequeueWrite33_5983368E292D7EA2B47CDCAA116EC7A6LL_4code15writeCompletiony10Foundation4DataV_AC6OpCodeOyycSgtFyyYbcfU_ (WebSocket.swift:1311)
4 myapp $sIegh_IeyBh_TR (:0)
5 Foundation NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK + 24
6 Foundation -[NSBlockOperation main] + 104
7 Foundation NSOPERATION_IS_INVOKING_MAIN + 16
8 Foundation -[NSOperation start] + 648
9 Foundation NSOPERATIONQUEUE_IS_STARTING_AN_OPERATION + 16
10 Foundation __NSOQSchedule_f + 172
11 libdispatch.dylib _dispatch_block_async_invoke2 + 148
12 libdispatch.dylib _dispatch_client_callout + 20
13 libdispatch.dylib _dispatch_continuation_pop + 600
14 libdispatch.dylib _dispatch_async_redirect_invoke + 584
15 libdispatch.dylib _dispatch_root_queue_drain + 392
16 libdispatch.dylib _dispatch_worker_thread2 + 156
17 libsystem_pthread.dylib _pthread_wqthread + 228
Steps to Reproduce
i am not sure the steps yet, If you need a clearer scenario, I can try to continue reproducing and investigating.
Expected behavior
I am unsure if this issue has been fixed before, and whether I can upgrade to the nearest stable version from my current one. And I prefer not to make a version leap that is too large.
Environment:
- OS/Version: arrange from 14.x to 18.x
- Starscream Version [e.g. 3.0.6]
- Xcode version : i use 15.2 to develop