Open danvk opened 9 years ago
Am I right in thinking that this is Chrome? I could reproduce in Chrome but not in Firefox.
I'm pretty certain there isn't a logic bug in the Dalliance .2bit fetching code -- instead, it's getting a bunch of zeroes back from a legitimate HTTP request. I suspect that this might be a bug in Chrome, most likely related to how results of partial (Range) requests get cached. I'll see if I can distill it down into something that can be submitted as a Chrome/Blink bug.
For now, I've made a small change which should prevent cached resources being used when fetching sequence. This will be included in the 0.12.8 and 0.13 releases unless we can come up with a better answer!
Chrome bug filed: https://code.google.com/p/chromium/issues/detail?id=416895
To reproduce:
Eventually you get to a region of all T's. IGV does not have such a region, and the pileups below also indicate that it's incorrect.