http://bugs.winehq.org/show_bug.cgi?id=28750
Bug #: 28750 Summary: Access violations and OLE errors using a WebBrowser based sample application Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: mshtml AssignedTo: wine-bugs@winehq.org ReportedBy: idw.doc@t-online.de Classification: Unclassified
PLease download and run my sample application for duplicating the crash(es), I'm not using Wine myself, but user's of my sample application reported several fatal errors when launching it: It's a simple HTML editor based on the IWebBrowser and MSHTML interfaces, available at http://idw-doc.homepage.t-online.de/PMUtils/IEWriter.zip.
A single URL parsing issue (in shlwapi) has already been fixed, see http://source.winehq.org/patches/data/79958.
http://bugs.winehq.org/show_bug.cgi?id=28750
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|mshtml |-unknown Severity|blocker |normal
--- Comment #1 from Dmitry Timoshkov dmitry@baikal.ru 2011-10-16 20:21:29 CDT --- Please read http://wiki.winehq.org/Bugs and missing information.
http://bugs.winehq.org/show_bug.cgi?id=28750
--- Comment #2 from Michael idw.doc@t-online.de 2011-10-17 08:25:32 CDT --- Sorry, I have absolutely no idea what's missing here, all you need to know for duplicating the issue is there. Looks pretty much (to me) like another case of blaming the user for a bad user interface: Just piling up lots of more or less relevant details on a separate page is *not* helpful for people not familiar with the bug tracking system nor the referred application (like me). Providing the relevant portions of it (plus samples) right at the spot (popups at hand) would certainly serve the purpose a lot better. In this case: If you ask a distinct question you'll get a distinct answer.
http://bugs.winehq.org/show_bug.cgi?id=28750
Jacek Caban jacek@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Status|UNCONFIRMED |NEW URL| |http://idw-doc.homepage.t-o | |nline.de/PMUtils/IEWriter.z | |ip CC| |jacek@codeweavers.com Component|-unknown |mshtml Version|unspecified |1.3.30 Ever Confirmed|0 |1
--- Comment #3 from Jacek Caban jacek@codeweavers.com 2011-10-17 08:42:47 CDT --- It fails because of missing IHTMLDocument2::get_frames implementation and later on get_scripts.
http://bugs.winehq.org/show_bug.cgi?id=28750
ocean04@suomi24.fi changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ocean04@suomi24.fi
--- Comment #4 from ocean04@suomi24.fi 2013-08-30 05:11:26 CDT --- I believe both functions are now implemented.
But it didn't work, wine-1.7.0-346-g1bf936c
http://bugs.winehq.org/show_bug.cgi?id=28750
--- Comment #5 from Nikolay Sivov bunglehead@gmail.com 2013-08-30 05:29:41 CDT --- Created attachment 45781 --> http://bugs.winehq.org/attachment.cgi?id=45781 +mshtml,+tid,+seh log
Now it hangs with stack overflow exception. Looks like it constantly tries to navigate to some warnpage.htm, this repeats over and over again:
--- 0042:trace:mshtml:HTMLDocument_put_URL (0x168f78)->(L"res://IEWriter.exe/warnpage.htm") ---
http://bugs.winehq.org/show_bug.cgi?id=28750
--- Comment #6 from Michael idw.doc@t-online.de 2013-09-03 14:33:52 CDT --- (In reply to comment #5)
Created attachment 45781 [details] +mshtml,+tid,+seh log
Now it hangs with stack overflow exception. Looks like it constantly tries to navigate to some warnpage.htm, this repeats over and over again:
Yes, it does this using the "res:" protocol as described at http://msdn.microsoft.com/en-us/library/aa767740(v=vs.85).aspx .
https://bugs.winehq.org/show_bug.cgi?id=28750
Damjan Jovanovic damjan.jov@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |damjan.jov@gmail.com
--- Comment #7 from Damjan Jovanovic damjan.jov@gmail.com --- Download link is dead. Is this application still available?
The bug might have been fixed already, eg. by 3e8bca0eb4f3f2c9b3bbf9fc634242512f8759b1 or thereabout.