Chrome Crashes After Temporary Operator Change on Windows 11
Bug #2005082 reported by
Jennifer Pringle
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Evergreen 3.9
Windows 11
Chrome 109.0.5414.120
In the last month I've had Chrome/Evergreen crash 3 times after I did an Operator Change to Temporary. It seems that Chrome/Evergreen crashes when Evergreen tries to timeout the temporary operator change. Chrome freezes and the only solution is to end the task via the Task Manager.
Looking into the task manager after this happens in Chrome my processor usage jumps to around 61/71% (looks like normal is around 10%) and my physical memory usage jumps to around 97%.
I have not managed to replicate this on purpose with the console open to check for errors but I will continue to try.
description: | updated |
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
To post a comment you must log in.
Does it make a difference whether the operator change is initiated from an AngularJS page or an Angular page?