(In reply to Simon Giesecke [:sg] [he/him] from comment #22) > > `JavaScript error: http://127.0.0.1/, line 31: ReferenceError: FuzzingFunctions is not defined` probably means that `fuzzing.enabled` is not set to `true`. > > I'm not sure what causes: `JavaScript error: http://127.0.0.1/, line 33: TypeError: e2.waitUntil is not a function`, but that was already happening in the original execution, so that's expected. Thank you, Simon! Verified again with 81.0a1(20200813213942), 80.0b8 (20200813191622), 68.12esr (20200813214232) and 78.2.0esr (20200813212801) on Ubuntu 18.04 and there are no tab crashes while loading the test case with `dom.fetchObserver.enabled` and `fuzzing.enabled` prefs enabled.
Bug 1656957 Comment 23 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Simon Giesecke [:sg] [he/him] from comment #22) > > `JavaScript error: http://127.0.0.1/, line 31: ReferenceError: FuzzingFunctions is not defined` probably means that `fuzzing.enabled` is not set to `true`. > > I'm not sure what causes: `JavaScript error: http://127.0.0.1/, line 33: TypeError: e2.waitUntil is not a function`, but that was already happening in the original execution, so that's expected. Thank you, Simon! Verified again with 81.0a1(20200813213942), 80.0b8 (20200813191622), 68.12esr (20200813214232) and 78.2.0esr (20200813212801) on Ubuntu 18.04 and there are no tab crashes while loading the test case with `dom.fetchObserver.enabled` and `fuzzing.enabled` prefs set on true.