Ned Andreev

I used to have this problem quite often, a few times per day, but after the recent update to Firefox 109 and after checking the `Use recommended performance settings` option,...

I still encounter it, but much more rarely than before, and I think it's a smaller version of the original bug :confused: Very rarely, a single Firefox window freezes (others...

:thinking: I don't remember seeing any signs of an OOM, but I haven't actually explicitly looked, I'll make sure to do so next time it happens! It's unlikely because the...

`TestTracer` seems to also be flaky: https://github.com/grafana/k6/pull/2960#issuecomment-1460021143

Thanks for confirming :bow: I added https://github.com/grafana/k6-docs/issues/946 to document this support better

Some of the same considerations I mentioned about `setup()` and `teardown()` in https://github.com/grafana/k6-operator/issues/223#issuecomment-1643722499 may also apply here :thinking: Though maybe not entirely, since for the best UX, I imagine it...

Just to be thorough, I've explained my proposal for native distributed execution in k6 (see https://github.com/grafana/k6/issues/3218 and https://github.com/grafana/k6/pull/3217). It's not meant to replace k6-operator, but rather to make k6-operator easier...

@neha13rb1998, you can define an `error` handler, see https://k6.io/docs/javascript-api/k6-ws/socket/socket-on-event-callback

@neha13rb1998, you can define a new custom metric (e.g. a `Counter`) and `add()` to it in the `error` websocket handler, see: - https://k6.io/docs/using-k6/metrics/#custom-metrics - https://k6.io/docs/javascript-api/k6-metrics/counter/

@neha13rb1998, move the `errorCounter.add(1);` in the body of the `socket.on('error', function(e){ ... }` function, like this: ```js socket.on('error', function(e){ if (e.error() != 'websocket: close sent') { errorCounter.add(1); console.log('An unexpected error...