Closed
Bug 1608793
Opened 5 years ago
Closed 5 years ago
Intermittent failure for iOS: unrecognized selector sent to instance 0x8000000000000000
Categories
(Data Platform and Tools :: Glean: SDK, defect, P3)
Data Platform and Tools
Glean: SDK
Tracking
(Not tracked)
RESOLVED
INACTIVE
People
(Reporter: janerik, Unassigned)
References
Details
(Whiteboard: [telemetry:glean-rs:m?])
Attachments
(1 file)
|
161.06 KB,
application/octet-stream
|
Details |
glean_sample_appUITests.DeletionRequestPingTest
testDeletionRequestPing, failed: caught "NSInvalidArgumentException", "-[NSTaggedPointerString countByEnumeratingWithState:objects:count:]: unrecognized selector sent to instance 0x8000000000000000"
DeletionRequestPingTest.swift:59
|
Reporter | |
Comment 1•5 years ago
|
||
|
|
Reporter | |
Updated•5 years ago
|
Summary: Intermitten failure for iOS: unrecognized selector sent to instance 0x8000000000000000 → Intermittent failure for iOS: unrecognized selector sent to instance 0x8000000000000000
|
|
Reporter | |
Comment 2•5 years ago
|
||
The stack points somewhere into Swifter (the HTTP server lib we're using in tests)
...
6 libswiftCore.dylib 0x000000012d4dc387 $sSh8IteratorV4nextxSgyF + 135
7 Swifter 0x000000012d3c4d81 $s7Swifter12HttpServerIOC4stopyyF + 385
...
A web search brings up a bunch of threading issues and race conditions. I think the same was happening here.
Some say compiling with optimizations got rid of the problem, but the way it is with threading issues/race conditions is that you can never be sure.
Keeping it open for a bit, monitoring if we see this issue again. Otherwise I'm going to label it an actual interkitten.
|
|
Reporter | |
Comment 3•5 years ago
|
||
Hasn't occured again to my knowledge.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•