Bug 28604
| Summary: | ASSERT(!resource->m_proxyResource) in CachedResource when surfing lexisnexis | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | David Levin <levin> |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ap, ggaren, koivisto, levin, simon.fraser |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://www.lexisnexis.com/ | ||
David Levin
Following the steps in https://bugs.webkit.org/show_bug.cgi?id=25399 (perhaps see the radar bugs), the ASSERT(!resource->m_proxyResource); in
CachedResource::setResourceToRevalidate may fire after using the lexisnexis site for some time.
(Using some notes from ap)
It seems to be due to a complicated combination of several frames including the
same script, and being reloaded using different navigation types at the same
time (like POST+reload or something) but an exact cause/repro hasn't been
determined yet.
Since there is logic that's supposed to prevent this sort of thing - preloaded
resources shouldn't be revalidated for normal loads - it's not good that it
breaks on lexisnexis.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Simon Fraser (smfr)
Also seeing this assertion loading a web archive of http://www.childrenscancer.org/zach/
Geoffrey Garen
This ASSERT reproduces for me running LayoutTests/cache/x-frame-options-304.html in a debug build in WebKit2 mode (while running the full test suite):
run-webkit-tests -2 --debug --batch-size=100000000 --iterations=8
Simon Fraser (smfr)
Saw this reloading http://www.polygon.com/e3-2014/2014/6/10/5792156/legend-of-zelda-wii-u-2015