Re: shdocvw: Implement IWebBrowser::ExecWB and IWebBrowser::QueryStatusWB.
On Thu, Jan 27, 2011 at 3:53 AM, Greg Geldorp <ggeldorp(a)vmware.com> wrote:
... Looking at http://test.winehq.org/data/tests/shdocvw:webbrowser.html, the shdocvw:webbrowser test doesn't have a history of occasional crashes. There are a few failures, but none of them are due to access violations. Which kind of indicates that the crash is because of the changes you made. I know it sucks to investigate failures that don't repro consistently, but I do think some more testing would be good here. Of course, if there's any info you need about the VM just let me know.
Well, I commandeered a XP SP3 box this morning and ran that exact same set of tests successfully 10,000 times. I don't have access to a Win7 box or I would have run the tests on that. Thoughts? Erich Hoover ehoover(a)mines.edu
From: Erich Hoover
On Thu, Jan 27, 2011 at 3:53 AM, Greg Geldorp <ggeldorp(a)vmware.com> wrote:
... Looking at http://test.winehq.org/data/tests/shdocvw:webbrowser.html, the shdocvw:webbrowser test doesn't have a history of occasional crashes. There are a few failures, but none of them are due to access violations. Which kind of indicates that the crash is because of the changes you made. I know it sucks to investigate failures that don't repro consistently, but I do think some more testing would be good here. Of course, if there's any info you need about the VM just let me know.
Well, I commandeered a XP SP3 box this morning and ran that exact same set of tests successfully 10,000 times. I don't have access to a Win7 box or I would have run the tests on that. Thoughts?
I'll do a similar test on Win7 tomorrow and let you know the results. Greg.
participants (2)
-
Erich Hoover -
Greg Geldorp