Steps to reproduce Apply the following diff to the client code (I tested against the v1.261.0 tag) diff --git a/src/sidebar/services/tags.js b/src/sidebar/services/tags.js index a897251d..8024bf2b ...
All of the crashes have occurred as I’m adding one or more tags to an annotation/highlight. I haven’t experienced a crash while creating annotation text.
The crash is immediate and complete and doesn’t just take out the individual tab, but the entirety of the Chrome processes. While it’s possible that this could be a Chrome issue, I’ve not experienced any crashes with any other websites in ages. I also know that there has been some new code and UI work around the interface and the way that tags are displayed in the public H product.
My initial guess is that something may be happening within the memory/caching as H tries to pull past tags from the server to guess what I’m typing.
I’ve alternated with using Firefox and the bookmarklet and have yet to see an issue with crashes there.
When browsing a website, Google Chrome (or any other browser) stores some data for speeding up the website pages load, in what's called Cache. This by default i
Repeat & Speed buttons for Vimeo HTML5 video
In a blog post, Google has admitted the newest version of Chrome rolling out to customers worldwide is going to consume up to 13% more of your system memory. For a browser whose biggest failing has long been its excessive memory consumption (1,2,3,4,5), this is the last thing users will want. Especially those with older systems and less RAM. Google also confirmed this is a cross-platform change and will apply to Chrome on Windows, Mac, Linux, and Chrome OS. The last of these could be particularly impacted as Chrome OS systems often ship with only 4-8GB of RAM.