http://bugs.winehq.org/show_bug.cgi?id=23441
Summary: WoW Battlechest launcher crashes Product: Wine Version: 1.2-rc5 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: mshtml AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com
With today's git, and rm -rf ~/.wine sh winetricks gecko sandbox for reproducibility, the script sh wisotool wowbc eventually crashes during the patching process as follows:
wine: Unhandled page fault on write access to 0x00000004 at address 0x7d8eb638 (thread 0036), starting debugger... Backtrace: =>0 nsChannel_Release+0x108(iface=0x1565d0) [include/wine/list.h:98] in mshtml 1 nsChannelBSC_destroy+0x19(bsc=0x156908) [dlls/mshtml/navigate.c:1022] 2 BindStatusCallback_Release+0x9d(iface=0x156908) [dlls/mshtml/navigate.c:302] 3 BindStatusCallback_Release+0x52(iface=0x29bc6e0) [dlls/urlmon/bindctx.c:124] 4 BSCServiceProvider_Release+0x12(iface=0x29bc6e4) [dlls/urlmon/bindctx.c:278] 5 Binding_Release+0x9d(iface=0x2a21d08) [dlls/urlmon/binding.c:852] 6 InternetBindInfo_Release+0x12(iface=0x2a21d10) [dlls/urlmon/binding.c:1162] 7 ProtocolHandler_Terminate+0x8d(iface=0x2a219e0, dwOptions=0) [dlls/urlmon/bindprot.c:676] 8 BindProtocol_Terminate+0x54(iface=0x2a219c8, dwOptions=0) [dlls/urlmon/bindprot.c:436] 9 InternetProtocolSink_ReportResult+0x75(iface=0x2a21d0c, hrResult=0, dwError=0, szResult=0x0(nil)) [dlls/urlmon/binding.c:1128] 10 report_result_proc+0x25(This=0x2a219c8, t=0x151078) [dlls/urlmon/bindprot.c:1141] 11 notif_wnd_proc+0x8f(hwnd=0x30068, msg=0x0465, wParam=0, lParam=0x2a219c8) [dlls/urlmon/bindprot.c:111] 12 WINPROC_wrapper+0x19() 13 call_window_proc+0x4c(hwnd=0x30068, msg=0x0465, wp=0, lp=0x2a219c8, result=0x33e264, arg=0x7d9592f0) [dlls/user32/winproc.c:242] 14 CallWindowProcW+0x48(func=0x7d9592f0, hwnd=0x30068, msg=0x0465, wParam=0, lParam=0x2a219c8) [dlls/user32/winproc.c:984]
This is the first run through for me, haven't checked how reproducible it is yet.
http://bugs.winehq.org/show_bug.cgi?id=23441
--- Comment #1 from Dan Kegel dank@kegel.com 2010-06-29 13:04:36 --- Oh, and here's what the autohotkey log says:
002: Run,/home/dank/.wisotool/cache/wowbc/WoW-3.2.0-enUS-patch.exe (0.11) 003: SetTitleMatchMode,2 004: WinWait,Blizzard Updater (23.20) 005: IfWinExist,Blizzard Updater,unable to start (0.00) 012: WinWait,Blizzard Updater,The update was successful (346.22) 013: ControlClick,Button1 (0.20) 014: WinWait,Launcher (1113.82)
so this was while waiting for the Launcher window to come up after applying the 3.2.0 patch by hand.
http://bugs.winehq.org/show_bug.cgi?id=23441
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Installer
--- Comment #2 from Dan Kegel dank@kegel.com 2010-06-29 13:10:53 --- Adding keyword installer since this happens while patching.
http://bugs.winehq.org/show_bug.cgi?id=23441
--- Comment #3 from Dan Kegel dank@kegel.com 2010-06-29 15:24:02 --- While doing wine WoW-3.3.0.10958-to-3.3.0.11159-enUS-downloader.exe to mimic what I think the autoupdate is doing (it left that exe there), I saw:
fixme:mshtml:nsHttpChannelInternal_SetDocumentURI (0x29d9c60)->() fixme:mshtml:nsChannel_SetReferrer (0x29d9c60)->(0x29a2210) fixme:mshtml:nsURI_GetUserPass default action not implemented fixme:mshtml:nsURL_GetQuery default action not implemented fixme:mshtml:nsURI_GetUserPass default action not implemented fixme:mshtml:nsURL_GetRef default action not implemented 0[15f3c0]: file (null), line 0: uncaught exception: [Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIDOMLocation.hash]" nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)" location: "JS frame :: wine:http://launcher.worldofwarcraft.com/2.0/_js/swfobject.js :: anonymous :: line 8" data: no]
Perhaps that's related. 'winetricks ie6' seems to work around this, and let the patch apply.
http://bugs.winehq.org/show_bug.cgi?id=23441
--- Comment #4 from Dan Kegel dank@kegel.com 2010-06-29 15:25:34 --- 'winetricks ie6' does not prevent the hang and then crash at 10% progress, though.
http://bugs.winehq.org/show_bug.cgi?id=23441
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh@gmail.com
--- Comment #5 from Jerome Leclanche adys.wh@gmail.com 2010-10-17 11:20:14 CDT --- Is this still an issue? I'm getting timeouts using wisotool wowbc
http://bugs.winehq.org/show_bug.cgi?id=23441
--- Comment #6 from Jerome Leclanche adys.wh@gmail.com 2011-07-17 07:23:19 CDT --- (In reply to comment #5) Dan, ping?
http://bugs.winehq.org/show_bug.cgi?id=23441
Jacek Caban jacek@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek@codeweavers.com
--- Comment #7 from Jacek Caban jacek@codeweavers.com 2011-08-01 05:06:42 CDT --- The problem from the above logs are fixed in current Wine, please retest
http://bugs.winehq.org/show_bug.cgi?id=23441
--- Comment #8 from Jerome Leclanche adys.wh@gmail.com 2011-10-26 06:46:49 CDT --- Dan, ping
http://bugs.winehq.org/show_bug.cgi?id=23441
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |ABANDONED
--- Comment #9 from Ken Sharp kennybobs@o2.co.uk 2013-08-16 07:52:49 CDT --- Three years should be long enough.
http://bugs.winehq.org/show_bug.cgi?id=23441
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Austin English austinenglish@gmail.com 2013-08-20 13:13:33 CDT --- Closing.
-
wine-bugs＠winehq.org