Browser: Runtime stability

[inancgumus]

What?

Stabilize the browser module in runtime.

Why?

To provide a better user experience and trust in running multi-VU browser tests safely.

Tasks

Major issues

Preview Give feedback

1. Deadlock one single iteration test xk6-browser#1253
   bug next +2
2. Run 1000+ VUs: Isolate browser contexts xk6-browser#1112
   8 of 8
   feature internal optimization performance team/k6browser +5
   
3. Deadlock: Multi-VU many iterations xk6-browser#971
   7 of 7
   bug remote team/k6browser +3
   
4. Deadlock: Navigation stops when request interception is enabled xk6-browser#1072
   10 of 10
   bug internal network manager remote +4
   
5. Browser hangs when waiting for the browserProc to close xk6-browser#1440
   3 of 3
   bug +1
   
6. Browser hangs once the test completes #4237
   area: browser bug +2
7. https://github.com/grafana/k6-cloud/issues/2868

Primary issues

Preview Give feedback

1. Move Sobek entirely out of the business logic #4219
   9 of 15
   area: browser refactor +2
   
2. Initiate internal goroutines after a component tree is ready #4238
   0 of 3
   area: browser bug +2
3. ElementHandle: nil pointer dereference #4123
   area: browser bug +2
   
4. Nil pointer dereference in session.Execute #4121
   area: browser bug +2
5. Concurrent map iteration and write bugs #4126
   0 of 4
   area: browser bug +2
6. IterEnd event handling leads to test abort (racy) #4239
   0 of 5
   area: browser bug +2
7. Panic on attaching iframe when getting browser window ID xk6-browser#1224
   2 of 2
   bug +1
   
8. Dispose: Cannot find context with specified id (-32000) xk6-browser#1144
   2 of 2
   bug +1
   
9. Data race due to concurrent map access xk6-browser#1066
   2 of 2
   bug next +2
   
10. Creating new page in browser context sometimes times out xk6-browser#966
    bug next remote +3
    
11. Concurrent write error with waitForEvent.js example script xk6-browser#1048
    bug next +2
    
12. Panic: Unexpected end of JSON input xk6-browser#987
    5 of 5
    bug remote +2
    
13. Deadlock: Another element is intercepting with pointer action xk6-browser#1004
    bug next remote +3

Several other issues might be related to the primary deadlock issues above.

Possible related issues

Preview Give feedback

1. Goroutine leaks #4241
   area: browser bug +2
2. Intermittent issues occur when using page.waitForNavigation() after element.click() #4242
   area: browser bug triage +3
3. Incorrect error message when docker image ran on ARM machine #4243
   area: browser bug +2
4. Dynamic URL cause high memory usage #4244
   area: browser bug triage +3
5. Deadlock: TestPageWaitForFunction xk6-browser#637
   bug +1
6. BrowserContext can't be created for reused VUs #4240
   area: browser bug triage +3
   
7. Clicking on a link that opens a new tab never navigates to the href link xk6-browser#827
   1 of 2
   bug next user request +3
   
8. frame.waitForSelector waits indefinitely xk6-browser#1252
   3 of 3
   bug user request +2
   
9. panic: runtime error: invalid memory address or nil pointer dereference xk6-browser#1148
   2 of 2
   bug +1
   
10. Nil when getting the DocumentID xk6-browser#577
    2 of 2
    bug next +2
    
11. Sobek runtime shouldn't be accessed while parsing options in async APIs xk6-browser#1162
    14 of 14
    bug +1
    
12. Remove Sobek from Execution Context Eval xk6-browser#1182
    8 of 8
    bug refactor +2
    
13. Investigate Uncaught (in promise) when evaluating JS: execution context changed xk6-browser#973
    bug next remote ux +4
    
14. Frame requestByID panics when initializing networking xk6-browser#986
    3 of 3
    bug next remote +3