From: Dmitry Timoshkov <dmitry@baikal.ru>
Subject: Re: [PATCH] ieframe: Fix position vs. length check in the go_forward() helper.
Message-Id: <20220124170424.f940091d9cd17a1b6722f43a@baikal.ru>
Date: Mon, 24 Jan 2022 17:04:24 +0300
In-Reply-To: <af39f3dc-d31b-57e7-3b2b-f4dca6f89f14@codeweavers.com>
References: <20220121133711.59cfff37d22d2a3aa513f396@baikal.ru> <E1nArZT-00049p-FS@winehq.org> <af39f3dc-d31b-57e7-3b2b-f4dca6f89f14@codeweavers.com>

Jacek Caban <jacek@codeweavers.com> wrote:

> On 1/21/22 11:55, Marvin wrote:
> > webbrowser.c:3341: Test failed: GoForward failed: 80004005
> > webbrowser.c:3342: Test failed: expected Invoke_BEFORENAVIGATE2
> > webbrowser.c:3345: Test failed: expected Invoke_COMMANDSTATECHANGE_NAVIGATEBACK_TRUE
> > webbrowser.c:3352: Test failed: expected Invoke_COMMANDSTATECHANGE_NAVIGATEFORWARD_FALSE
> > webbrowser: Timeout
> 
> 
> FWIW, those failures seem valid and related to the patch.

Right. The real culprit of the crashes that I observe locally is caused
by a reused history entry with invalid entry->stream. I'll send another
patch that fixes the crashes.

-- 
Dmitry.