Thanks for the detailed reply, Dan. All good information to have. We're going to try Garry's solution and see if it works: "Try going into Chrome settings -> performance and turn off preload pages." So far so good, but it's only been a few minutes.
John John Amundson | Library Applications Supervisor | CW MARS jamund...@cwmars.org | 508-755-3323 x1 <5087553323p1> https://www.cwmars.org he/him/his <https://www.mypronouns.org/he-him> On Tue, Nov 7, 2023 at 1:51 PM Daniel Guarracino <dguarrac...@owwl.org> wrote: > Hi John, > > We've also encountered intermittent Hatch issues recently that are exactly > as you describe. > > We had two reports of this behavior the week of October 23. At the time, > we were also on 3.7.3. Both libraries that were affected encountered > incomplete page loads only when accessing bookmarks (such as for Checkout, > Item Status, etc.) while Hatch was enabled. If the affected libraries > reloaded a page after the incomplete page load OR if the bookmark was > clicked twice in quick succession (innovative!), it would load completely > without fail. If Hatch was disabled or if links were accessed using the > links within Evergreen's interface, the page loaded just fine -- no > workaround necessary. > > I took a look at the extensions logs on an affected machine. Hatch is > exhibiting the same type of behavior as it had in late 2021 with these > incomplete page loads, where the port for the tab is disconnected and Hatch > does not respond to the message it is sent. > > We upgraded to 3.11.1 at the end of last week, so I wanted to wait to see > if the upgrade somehow resolved the Hatch-related problems before trying to > figure these out, especially since two of our libraries were affected. > Unfortunately, at least one of the libraries is still encountering problems > with bookmarks. And, funny enough, we've had two more libraries report what > sounds like the same problem within the past hour or so. > > Since the upgrade to 3.11, we've also encountered another Hatch-related > issue. I'm not sure if it's the same root cause, but I figured I'd mention > it: With Hatch enabled, opening Evergreen's home button in a new tab > results in being asked to register a workstation. This behavior isn't > encountered when Hatch is disabled. It's only encountered when opening the > splash page via that home button in a new tab; opening in the same tab > works fine. > > So, +1 to the idea that something has recently caused Hatch to start > misbehaving. > > Dan > > -- > Daniel Guarracino > Automation Services Librarian > OWWL Library System > 2557 State Route 21 > Canandaigua, NY 14424 > 585.394.8260 x1104 > > ------------------------------ > *From: *"Evergreen-general" <evergreen-general@list.evergreen-ils.org> > *To: *"Evergreen-general" <evergreen-general@list.evergreen-ils.org> > *Cc: *"John Amundson" <jamund...@cwmars.org> > *Sent: *Tuesday, November 7, 2023 1:30:07 PM > *Subject: *[Evergreen-general] Inconsistent White Screens with Hatch > > Hello! > > Historically we've found that bad installations of Hatch can lead to > blank/white screens in Evergreen, and reinstalling Hatch usually resolves > this. > > However, over the last week or so, we've started to receive reports of > blank/white screens that we cannot seem to resolve. The problem is slightly > different from historical reports in that the white screens do not appear > every time, and they are more likely to appear when accessing a web client > page from a bookmark than within the client. Refreshing a blank page can > sometimes force it to load correctly. It's the inconsistency that's making > this hard to nail down. > > Has anyone else run into this issue and have you had any luck in resolving > it? We've gotten a total of 5 reports over the last week or so. > > Some information about our setup: > > - Running Evergreen 3.73 plus some newer features > - Affecting (at least) Chrome 119.0.6045.105 and 119.0.6045.106 > - Affecting (at least) Hatch version 0.3.2 and 0.3.3. > > And what we've tried: > > - Clearing cache > - Updating/recreating bookmarks > - Updating Chrome > - Updating Hatch > - Reinstalling Hatch > - Clearing site settings and cookies > - Removing eg.hatch.login_keys from in-browser preferences > > The only way we've found to stop it completely is to disable Hatch, which > some of our libraries rely on heavily. > > When a page fails to load, the console seems to hang up on this message: > [image: image.png] > > Anyone have any thoughts or suggestions? > > Thank you! > > John > > John Amundson | Library Applications Supervisor | CW MARS > > jamund...@cwmars.org | 508-755-3323 x322 > > https://www.cwmars.org > > he/him/his <https://www.mypronouns.org/he-him> > > _______________________________________________ > Evergreen-general mailing list > Evergreen-general@list.evergreen-ils.org > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general > >
_______________________________________________ Evergreen-general mailing list Evergreen-general@list.evergreen-ils.org http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general