(In reply to Dennis Schubert [:denschub] from comment #3) > The linked community thread is about ESR 115, which is... very old. It seems fine with newer releases, although there is a chance we see some rare intermittent issues? FWIW the reporter here (Adam) seems to have been using Firefox 139, so this probably isn't ESR-specific. The last two posts in the [linked thread](https://community.openai.com/t/chatgpt-has-stopped-working-in-firefox/664425/102) seem to have found a relevant `TypeError` and potentially an intervention that works for the person who noticed it there Quoting those posts: > If you look in the console you’ll a lot of warnings and in my case, an error at the top saying_ > `Uncaught (in promise) TypeError: Performance.mark: Expected startTime >= 0` > My hunch is that maybe Firefox doesn’t allow Performance.mark to have a startTime < 0, > but OpenAI (or a package they use) is doing some funk with specific timings and state causing a race-condition. Note: the thing about negative startTime isn't Firefox-specific; this gives a TypeError in both Firefox and Chrome: ``` performance.mark("my mark", {startTime: -5}) ``` But it's possible that OpenAI has a race condition that happens to trigger this negative-startTime situation in a Firefox-specific way, I suppose. The reporter has a screenshot of DevTools showing some of the relevant code: https://us1.discourse-cdn.com/openai1/optimized/4X/9/1/6/9164b581a5c70e3617630bcec2e059bf5249b5b8_2_1035x424.png and they confirmed that hacking around this negative-startTime does fix the issue for them.
Bug 1972808 Comment 4 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 Dennis Schubert [:denschub] from comment #3) > The linked community thread is about ESR 115, which is... very old. It seems fine with newer releases, although there is a chance we see some rare intermittent issues? FWIW the reporter here (Adam) seems to have been using Firefox 139, so this probably isn't ESR-specific. The last two posts in the [linked thread](https://community.openai.com/t/chatgpt-has-stopped-working-in-firefox/664425/102) seem to have found a relevant `TypeError` and potentially an intervention that works for the person who noticed it there Quoting those posts: > If you look in the console you’ll a lot of warnings and in my case, an error at the top saying_ > `Uncaught (in promise) TypeError: Performance.mark: Expected startTime >= 0` > My hunch is that maybe Firefox doesn’t allow Performance.mark to have a startTime < 0, > but OpenAI (or a package they use) is doing some funk with specific timings and state causing a race-condition. Note: the thing about negative startTime isn't Firefox-specific; the following JS snippet (executed in DevTools console) gives a TypeError in both Firefox and Chrome: ``` performance.mark("my mark", {startTime: -5}) ``` But it's possible that OpenAI has a race condition that happens to trigger this negative-startTime situation in a Firefox-specific way, I suppose. The reporter has a screenshot of DevTools showing some of the relevant code: https://us1.discourse-cdn.com/openai1/optimized/4X/9/1/6/9164b581a5c70e3617630bcec2e059bf5249b5b8_2_1035x424.png and they confirmed that hacking around this negative-startTime does fix the issue for them.