Bug 16952 – Reproducible assertion failure in FrameLoader::restoreScrollPositionAndViewState() (m_currentHistoryItem)

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: Page Loading

See also bug 13684 <rdar://problem/5203036>.

ASSERTION FAILED: m_currentHistoryItem
(WebCore/loader/FrameLoader.cpp:3916 void WebCore::FrameLoader::restoreScrollPositionAndViewState())

Steps to reproduce:
1) Go to the URL.
2) Click the black&white photo.

Reduction: enter the following in the address bar:
javascript: window.open().location.reload()

[Mark Rowe (bdash)]

What's the impact of this in a release build?

[Mark Rowe (bdash)]

Just looked at the code:

    ASSERT(m_currentHistoryItem);
    
    // FIXME: As the ASSERT attests, it seems we should always have a currentItem here.
    // One counterexample is <rdar://problem/4917290>
    // For now, to cover this issue in release builds, there is no technical harm to returning
    // early and from a user standpoint - as in the above radar - the previous page load failed 
    // so there *is* no scroll or view state to restore!
    if (!m_currentHistoryItem)
        return;


In a release build this would seem to be harmless.

[Mark Rowe (bdash)]

<rdar://problem/5697153>

[Ahmad Saleem]

*** This bug has been marked as a duplicate of bug 252944 ***