16952 2008-01-20 21:23:44 -0800 Reproducible assertion failure in FrameLoader::restoreScrollPositionAndViewState() (m_currentHistoryItem) 2023-10-03 10:50:20 -0700 1 1 1 Unclassified WebKit Page Loading 528+ (Nightly build) Mac OS X 10.5 RESOLVED DUPLICATE 252944 https://bugs.webkit.org/show_bug.cgi?id=252944 http://www.leviahon.co.il/article.php?id=637 HasReduction, InRadar P2 Normal --- 1 mitz webkit-unassigned ahmad.saleem792 tevaum oldest_to_newest 67820 0 mitz 2008-01-20 21:23:44 -0800 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. 67821 1 mitz 2008-01-20 21:34:34 -0800 Reduction: enter the following in the address bar: javascript: window.open().location.reload() 67822 2 mrowe 2008-01-20 21:44:13 -0800 What's the impact of this in a release build? 67823 3 mrowe 2008-01-20 21:45:48 -0800 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. 67824 4 mrowe 2008-01-20 21:47:23 -0800 <rdar://problem/5697153> 1982144 5 ahmad.saleem792 2023-10-03 10:50:20 -0700 *** This bug has been marked as a duplicate of bug 252944 ***