Chrome Crashes After Temporary Operator Change on Windows 11

[Jennifer Pringle]

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.

[Galen Charlton (gmc)]

Does it make a difference whether the operator change is initiated from an AngularJS page or an Angular page?

[Tiffany Little (tslittle)]

This sounds very similar to what I experienced with bug 2002693. Same thing happened to me with the processor/physical memory usage too.

[Lena Hernandez (lfhernandez)]

I tested under the same situation (EG 3.9, W 11, C 109.0.5414.120) and was unable to recreate the bug. I tried from both an AngularJS (User Permission Editor) and Angular (Booking Administrator) pages.

[Jennifer Pringle (jpringle-u)]

The most recent time this happened to me I had done the Operator Change from the reporter, so XUL??

The first two times I'm pretty sure I was in Fund Administration or the acq General Search, so Angular.

I've tried a few times to recreate this while having the console open on the tab I did Operator Change on but each time Evergreen timesout and logs out normally.

I think the major difference so far between when it happens and my attempts to recreate is how much I've used Evergreen. Generally when it happens I've been doing multiple things in Evergreen and have had it open for a while. For my tests so far I've usually done a couple things and haven't had Evergreen open for very long (I'll try to replicate after I've been doing more with Evergreen).

[Jennifer Pringle (jpringle-u)]

I kind of managed to replicate on purpose.

I did Change Operator on the reporter and Chrome froze temporarily (for about 2 minutes) while timing out/logging out.

I'd been working with the acq general search and shelving location editor as well as running some reports in the reporter before changing the operator.

I get the following in the console:

DevTools failed to load source map: Could not load content for https://catalogue.libraries.coop/upup.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for https://catalogue.libraries.coop/js/ui/default/staff/build/js/moment-with-locales.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for https://catalogue.libraries.coop/js/ui/default/staff/build/js/lovefield.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for https://catalogue.libraries.coop/js/ui/default/staff/build/js/iframeResizer.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for https://catalogue.libraries.coop/js/ui/default/staff/build/css/bootstrap.min.css.map: Load canceled due to load timeout
egAuth found no core.bundle.js:1 valid authtoken

The processor and physical memory usage was higher than normal, but not nearly what I saw before, and is slowly decreasing back to normal.

[Galen Charlton (gmc)]

Thanks, Jennifer. How many tabs did you have going at the time?

[Jennifer Pringle (jpringle-u)]

I think I had about 15-20 tabs going in Chrome at the time. About 5 tabs were logged into the Evergreen server where I did change operator. As well, I had about 5 tabs logged into our training server which I was actively using when Chrome froze.

[Tiffany Little (tslittle)]

This just happened to me, so adding my experience. I only had 5 tabs open in Chrome--I think I only had one tab open for EG. I had been doing temporary operator changes and flipping between logins because I was testing permissions. But I was in the middle of working--I had just done an operator change maybe a minute or two before--when I was forcibly logged out. It takes you back to the sign-in screen, but the indicator bars on the fields are gray instead of green/red and you can't do anything in Chrome. You can't click on anything to open the console log, or change tabs. You have to kill it from the task manager. CPU and Memory both spiked super high (my CPU was at 96%).