Summary: | REGRESSION (r172660): WebKit2.TerminateTwice asserts | ||
---|---|---|---|
Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> |
Component: | WebKit2 | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | andersca, ddkilzer, kling, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=162624 | ||
Bug Depends on: | 162077 | ||
Bug Blocks: |
Description
Alexey Proskuryakov
2014-08-15 19:49:52 PDT
This is an interesting issue. This test checks for a quick crash in a code path that is still obviously and seriously broken (as far as I can tell). Doing what the test does corrupts WebKit2 data structures in a way that will cause crashes and other bugs later. So r172660 added an assertion to catch Safari and other clients doing this. So the options are to either remove the assertion and keep the test, or to keep the assertion and remove the test. The fact that the assertion started to fail doesn't mean that anything regressed, it's just a new assertion. Given the above, I think that keeping the assertion is more valuable. Skipped the test (in debug mode only) in <http://trac.webkit.org/r172680>. This ASSERT was accidentally commented out in r204916 for Bug 161103: <http://trac.webkit.org/changeset/204916> I'm assuming the ASSERT is still valid, so will be posting a patch to restore it. I filed: Bug 162077: ASSERT accidentally commented out in r204916 (In reply to comment #3) > This ASSERT was accidentally commented out in r204916 for Bug 161103: > > <http://trac.webkit.org/changeset/204916> > > I'm assuming the ASSERT is still valid, so will be posting a patch to > restore it. > > I filed: Bug 162077: ASSERT accidentally commented out in r204916 The ASSERT was re-enabled by: Committed r206040: <http://trac.webkit.org/changeset/206040> Was fixed with the fix for 162938. *** This bug has been marked as a duplicate of bug 162938 *** |