Closed KatieWoe closed 2 years ago
I was kind of able to duplicate this by fuzzing the unbuilt version on my development machine. I say "kind of" because it wasn't exactly the same stack trace, but it was similar, see below. In both, press listeners and PhetIoObjects are involved. I did some looking around, and there is a recent commit to PressListener
that references PhetIoObject
, specifically https://github.com/phetsims/scenery/commit/fe972864d061e07203e5dd7ae4720916502a5e2f.
@zepumph - Can you please take a look and see if you think this change introduced this CT error? If not, assign back to me and I'll do more investigation.
Stack trace from local test:
window.assertions.assertFunction (assert.js:23)
emit (TinyEmitter.ts:72)
emit (Emitter.ts:66)
execute (PhetioAction.ts:97)
release (PressListener.ts:503)
pointerUp (PressListener.ts:815)
dispatchToListeners (Input.ts:1822)
dispatchEvent (Input.ts:1772)
upEvent (Input.ts:1572)
Input.mouseUpAction.PhetioAction.phetioPlayback (Input.ts:389)
execute (PhetioAction.ts:95)
mouseUp (Input.ts:1220)
mouseToggle (InputFuzzer.js? [sm]:266)
InputFuzzer.mouseToggleAction (InputFuzzer.js? [sm]:40)
fuzzEvents (InputFuzzer.js? [sm]:105)
fuzzInputEvents (SimDisplay.js? [sm]:179)
runAnimationLoop (Sim.js? [sm]:918)
requestAnimationFrame (async)
.
.
.
I think this is the state-wrapper version of https://github.com/phetsims/joist/issues/790, fixed by https://github.com/phetsims/tandem/commit/3f93369bc64e4ffdb3a5e7fdfc3e97f9b7d108e1.
Sorry that you dove into my mistake here. I cannot reproduce in 2 minutes of fuzzing plus the time it took to write this message. I also noted that the CT state test for BAA has passed multiple times since the two-in-a-row failure of this problem yesterday.