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

Primary issues

Beta Give feedback

1. Deadlock one single iteration test #1253
   bug +1
2. Initiate internal goroutines after a component tree is ready #1247
   0 of 3
   bug evaluate events internal +4
3. Move Goja entirely out of the business logic #1064
   2 of 15
   epic productivity refactor stability +4
   
4. ElementHandle: nil pointer dereference #1056
   bug user request +2
5. Nil pointer dereference in session.Execute #1208
   bug +1
6. Panic on attaching iframe when getting browser window ID #1224
   bug +1
7. Dispose: Cannot find context with specified id (-32000) #1144
   2 of 2
   bug +1
   
8. Deadlock: Navigation stops when request interception is enabled #1072
   10 of 10
   bug internal network manager remote +4
   
9. Isolate browser contexts between iterations #1112
   8 of 8
   feature internal optimization performance team/k6browser +5
   
10. Deadlock: Multi-VU many iterations #971
    7 of 7
    bug remote team/k6browser +3
    
11. Data race due to concurrent map access #1066
    2 of 2
    bug next +2
    
12. Creating new page in browser context sometimes times out #966
    bug next remote +3
    
13. Concurrent write error with waitForEvent.js example script #1048
    bug next +2
    
14. Panic: Unexpected end of JSON input #987
    5 of 5
    bug remote +2
    
15. Deadlock: Another element is intercepting with pointer action #1004
    bug next remote +3

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

Other issues

Beta Give feedback

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