chrome version 61.0.3163.100: " net::ERR_CACHE_OPERATION_NOT_SUPPORTED" on bigWig track

[paul-shannon]

Chrome's automatic self-update to version 61.0.3163.100 yesterday coincided precisely with recurrent net::ERR_CACHE_OPERATION_NOT_SUPPORTED errors executing this function call:

igv.browser.loadTrack(
      {url: 'https://s3.amazonaws.com/igv.broadinstitute.org/data/hg19/encode/wgEncodeBroadHistoneGm12878H3k4me3StdSig.bigWig',
       name: 'H3k4me3'
      })

I had been working successfully all morning with local and remote bigWig files, pleased at the way igv handles them. Then repeated failures. The error disappears now that I have installed an older version of Chrome (59.0.3071.86). Also no error with FireFox.

A websearch of the error turned up a few mentions of "byte range requests" in association with this error.

Any ideas? Is this just a Chrome bug which we hope they fix?

[jrobinso]

Hi Paul, What version of igv.js are you running? I am on Chrome Version 61.0.3163.100 (Official Build) (64-bit) also and am not having this issue. I've seen that error before when running igv.js with chrome developer tools, IIRC clearing the cache resolved it. I do think its a problem with their cache when range requests are used. In recent versions of igv.js I started adding a random number as a parameter value to urls to try to prevent caching, I can't recall exactly when that was added.

…

On Thu, Sep 28, 2017 at 3:47 PM, Paul Shannon ***@***.***> wrote: Chrome's automatic self-update to version 61.0.3163.100 yesterday coincided precisely with recurrent net::ERR_CACHE_OPERATION_NOT_SUPPORTED errors executing this function call: igv.browser.loadTrack( {url: 'https://s3.amazonaws.com/igv.broadinstitute.org/data/hg19/encode/wgEncodeBroadHistoneGm12878H3k4me3StdSig.bigWig', name: 'H3k4me3' }) I had been working successfully all morning with local and remote bigWig files, pleased at the way igv handles them. Then repeated failures. The error disappears now that I have installed an older version of Chrome (59.0.3071.86). Also no error with FireFox. A websearch of the error turned up a few mentions of "byte range requests" in association with this error. Any ideas? Is this just a Chrome bug which we hope they fix? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#424>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA49HLJInjubcilav0nNc0I6nEXdJ0cjks5snCIJgaJpZM4Pn_Mw> .

[paul-shannon]

Hi Jim,
I see the error consistently on chrome 61.0.3163.100 with igv-1.0.9.js

• Paul

[jrobinso]

Well, googling the error I found out that I did introduce a change in the master branch that fixed this for some: igvteam/igv#464 Could you try the beta igv and see if it fixes the problem for you? Again I've not been able to reproduce it with 61.0.3163.100. This will become the official release soon. https://igv.org/web/beta/igv-beta.js https://igv.org/web/beta/igv-beta.css

…

On Fri, Sep 29, 2017 at 9:55 AM, Paul Shannon ***@***.***> wrote: Hi Jim, I see the error consistently on chrome 61.0.3163.100 with igv-1.0.9.js - Paul — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#424 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA49HMjEcn1ZwfrPn7mvRTHuxpUgnUpLks5snSEGgaJpZM4Pn_Mw> .

[paul-shannon]

Hi Jim, igv-beta works beautifully with bigWig and chrome 61.0.3163.100. Thank you! - Paul

…

On Sep 29, 2017, at 8:00 PM, Jim Robinson ***@***.***> wrote: Well, googling the error I found out that I did introduce a change in the master branch that fixed this for some: igvteam/igv#464 Could you try the beta igv and see if it fixes the problem for you? Again I've not been able to reproduce it with 61.0.3163.100. This will become the official release soon. https://igv.org/web/beta/igv-beta.js https://igv.org/web/beta/igv-beta.css On Fri, Sep 29, 2017 at 9:55 AM, Paul Shannon ***@***.***> wrote: > Hi Jim, > I see the error consistently on chrome 61.0.3163.100 with igv-1.0.9.js > > - Paul > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#424 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AA49HMjEcn1ZwfrPn7mvRTHuxpUgnUpLks5snSEGgaJpZM4Pn_Mw> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[jrobinso]

OK, we're wrapping up the last bits to release this soon. On Mon, Oct 2, 2017 at 10:36 AM, Paul Shannon <notifications@github.com> wrote:

…

Hi Jim, igv-beta works beautifully with bigWig and chrome 61.0.3163.100. Thank you! - Paul > On Sep 29, 2017, at 8:00 PM, Jim Robinson ***@***.***> wrote: > > Well, googling the error I found out that I did introduce a change in the > master branch that fixed this for some: > igvteam/igv#464 > > Could you try the beta igv and see if it fixes the problem for you? Again > I've not been able to reproduce it with 61.0.3163.100. This will become > the official release soon. > > https://igv.org/web/beta/igv-beta.js > https://igv.org/web/beta/igv-beta.css > > On Fri, Sep 29, 2017 at 9:55 AM, Paul Shannon ***@***.***> > wrote: > > > Hi Jim, > > I see the error consistently on chrome 61.0.3163.100 with igv-1.0.9.js > > > > - Paul > > > > — > > You are receiving this because you commented. > > Reply to this email directly, view it on GitHub > > <#424 (comment)>, or mute > > the thread > > <https://github.com/notifications/unsubscribe-auth/ AA49HMjEcn1ZwfrPn7mvRTHuxpUgnUpLks5snSEGgaJpZM4Pn_Mw> > > . > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread. > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#424 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA49HAEHKRKJUqcSVnBiuxztP20eU8ISks5soR8lgaJpZM4Pn_Mw> .

[sporkman]

I'm seeing this error in another context with Chrome, and I'm just groping around in the dark. Can you explain what the root cause of the Chrome issue is and what your fix involved?

[jrobinso]

I don't know what the root cause is, but Chrome does not do a good job of caching requests with range-byte headers. To fix it I added a parameter with a random seed to every request, which makes it appear to the browser to be a unique URL, like this "&someRandomSeed=" + Math.random().toString( 36);

…

On Thu, Oct 12, 2017 at 6:02 PM, sporkman ***@***.***> wrote: I'm seeing this error in another context with Chrome, and I'm just groping around in the dark. Can you explain what the root cause of the Chrome issue is and what your fix involved? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#424 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA49HMRcKwYEPz28FRIyd96l1G4osZAnks5srratgaJpZM4Pn_Mw> .