[Bug 37306] New: ApexDC crashes on start with wine configured as Vista or higher
https://bugs.winehq.org/show_bug.cgi?id=37306 Bug ID: 37306 Summary: ApexDC crashes on start with wine configured as Vista or higher Product: Wine Version: 1.7.26 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hk-wine(a)circlestorm.org ApexDC 1.6.0 x86_64 version ( http://www.apexdc.net/download/ ) ApexDC shows a crash dialog box with no interesting info, however it says that I should run it with the .pdb file to get a debug trace that could be reported to the ApexDC team. However, the .pdb file is already there so possibly that is the FindFirstFileExW bug also causing the failed debug (Bug 37305). $ wine ApexDC-x64.exe fixme:wincodecs:PngDecoder_Block_GetCount stub fixme:module:load_library unsupported flag(s) used (flags: 0x00000800) fixme:advapi:RegisterTraceGuidsW (0x14031ca58, (nil), {f7b697a3-4db5-4d3b-be71-c4d284e6592f}, 7, 0x1404824d0, (null), (null), 0x1404b55a8): stub fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37306 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, win64 Status|UNCONFIRMED |NEW URL| |http://www.apexdc.net/downl | |oad/ CC| |focht(a)gmx.net Component|-unknown |kernel32 Summary|ApexDC crashes on start |64-bit ApexDC 1.6.0 crashes |with wine configured as |on startup with Wine |Vista or higher |configured as Vista or | |higher (needs Thread Pool | |Timer API, | |'CreateThreadpoolTimer') Ever confirmed|0 |1 --- Comment #1 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, confirming. --- snip --- $ pwd /home/focht/wine64/drive_c/Program Files/ApexDC++ $ WINEDEBUG=+tid,+seh,+relay wine ./ApexDC-x64.exe >>log.txt 2>&1 ... 0025:Call KERNEL32.CreateEventExW(00000000,00000000,00000000,001f0002) ret=140304c20 0025:Ret KERNEL32.CreateEventExW() retval=00000084 ret=140304c20 0025:Call KERNEL32.RegisterWaitForSingleObject(00085280,00000084,14031bc7c,00084fb0,ffffffff,00000000) ret=140317aff 0025:Ret KERNEL32.RegisterWaitForSingleObject() retval=00000001 ret=140317aff 0025:Call KERNEL32.GetLastError() ret=140317b6a 0025:Ret KERNEL32.GetLastError() retval=00000000 ret=140317b6a 0025:Call ntdll.RtlPcToFileHeader(14047b018,0033f4b0) ret=14030c43c 0025:Ret ntdll.RtlPcToFileHeader() retval=140000000 ret=14030c43c 0025:Call KERNEL32.RaiseException(e06d7363,00000001,00000004,0033f480) ret=14030c47b 0025:trace:seh:raise_exception code=e06d7363 flags=1 addr=0x7b84ad13 ip=7b84ad13 tid=0025 0025:trace:seh:raise_exception info[0]=0000000019930520 0025:trace:seh:raise_exception info[1]=000000000033f518 0025:trace:seh:raise_exception info[2]=000000014047b018 0025:trace:seh:raise_exception info[3]=0000000140000000 0025:trace:seh:raise_exception rax=000000000033f260 rbx=000000014047b018 rcx=000000000033f260 rdx=0000003157349c5c 0025:trace:seh:raise_exception rsi=000000000033f480 rdi=000000000033f280 rbp=000000000033f3b0 rsp=000000000033f240 0025:trace:seh:raise_exception r8=0000000000000004 r9=000000000033f480 r10=0000000000000000 r11=00000031573807e0 0025:trace:seh:raise_exception r12=0000000140325970 r13=0000000000000001 r14=00000000ffffffff r15=0000000000000000 ... 0025:trace:seh:call_stack_handlers found wine frame 0x33fe80 rsp 33ff90 handler 0x7f2b7ca3dabe 0025:trace:seh:call_teb_handler calling TEB handler 0x7f2b7ca3dabe (rec=0x33f260, frame=0x33fe80 context=0x33e4f0, dispatcher=0x33df78) 0025:Call KERNEL32.UnhandledExceptionFilter(0033df00) ret=7f2b7ca3db14 0025:Call dbghelp.SymSetOptions(00000214) ret=140056bd4 0025:Ret dbghelp.SymSetOptions() retval=00000214 ret=140056bd4 0025:Call dbghelp.SymInitialize(ffffffffffffffff,00000000,00000001) ret=140056be9 --- snip --- The app provides a .PDB file on its own which improves the backtrace but doesn't reveal it: --- snip --- Wine-dbg>bt Backtrace: =>0 0x000000007b84ad13 RaiseException+0xe5(code=0xe06d7363, flags=0x1, nbargs=0x4, args=0x33f480) [/home/focht/projects/wine/wine.repo/src/dlls/kernel32/except.c:85] in kernel32 (0x000000000033f430) 1 0x000000014030c47b _CxxThrowException+0xb2(pExceptionObject=0x140000000, pThrowInfo=0x4, ThisException={ExceptionCode=0xe06d7363, ExceptionFlags=0x1, ExceptionRecord=(nil), ExceptionAddress=0x0(nil), NumberParameters=0x4, params={magicNumber=0x19930520, pExceptionObject=0x33f518, pThrowInfo=0x14047b018, pThrowImageBase=0x140000000}}, ThrowImageBase=0x140000000) [f:\dd\vctools\crt\crtw32\eh\throw.cpp:152] in apexdc-x64 (0x000000000033f4a0) 2 0x0000000140317b93 Concurrency::details::SchedulerBase::SchedulerBase+0x37e(this=0x5de70, policy=0x33f670) in apexdc-x64 (0x0000000000000001) 3 0x000000014033394c Concurrency::details::ThreadScheduler::ThreadScheduler+0x1f(this=0x33f670, policy=(nil)) in apexdc-x64 (0x000000000033f770) 4 0x0000000140333a53 Concurrency::details::ThreadScheduler::Create+0x32(policy=0x1404b5ba4) in apexdc-x64 (0x000000000033f770) 5 0x0000000140318b1f Concurrency::details::SchedulerBase::CreateWithoutInitializing+0x1a(policy=0x33f6d0) in apexdc-x64 (0x000000000033f770) 6 0x00000001403195c8 Concurrency::details::SchedulerBase::GetDefaultScheduler+0x93(_lock={_M_lock=0x1404b5ba8}, policy={_M_pPolicyBag=0x59e20}) in apexdc-x64 (0x000000000033f770) 7 0x0000000140318aaf Concurrency::details::SchedulerBase::CreateContextFromDefaultScheduler+0xe() in apexdc-x64 (0x000000000033f770) 8 0x0000000140301140 Concurrency::Alloc+0x3b(numBytes=0x1) in apexdc-x64 (0x000000000033f770) 9 0x00000001400914e8 Concurrency::task<void>::task<void><<lambda_8cd0909e66f4ef6ba8bd8e574cd09e31>
+0x127(this=0x33f820, _Param={__this=0x569d0}, _TaskOptions=0x1) in apexdc-x64 (0x000000000033f770)
10 0x0000000140091311 Concurrency::create_task<<lambda_8cd0909e66f4ef6ba8bd8e574cd09e31>
+0x70(_Param={__this=0x569d0}, _TaskOptions=0x33f838) in apexdc-x64 (0x000000000033f849)
11 0x0000000140090be9 std::_Task_async_state<void,0>::_Task_async_state<void,0><std::_Bind<0,void,<lambda_70b49fd59b39f0ea1cab861673d1f5d2>
+0x9c(this=0x569d0, _Fnarg=0x33fa60) in apexdc-x64 (0x000000000033f849)
12 0x000000014009073f std::_Async<<lambda_70b49fd59b39f0ea1cab861673d1f5d2>
+0x52(_Fnarg=0x569d0, _Pr={_State={_Assoc_state=(nil), _Get_only_once=false}, _Future_retrieved=false}) in apexdc-x64 (0x000000000033f930)
13 0x000000014009011d std::async<enum std::launch,<lambda_70b49fd59b39f0ea1cab861673d1f5d2> >+0x2c(_Fnarg=0x55c60) in apexdc-x64 (0x000000000033fa90) ... 17 0x000000007b87d2d2 call_process_entry+0x1c(peb=0x7fffff7ef000, entry=0x140309b7c) [/home/focht/projects/wine/wine.repo/src/dlls/kernel32/process.c:1066] in kernel32 (0x000000000033fd20) --- snip --- With some debugging I figured out the app requires some Vista+ Thread Pool Timer API in Vista+ mode. The runtime code late-binds various imports. Missing imports don't cause immediate failure as the actual async thread/timer wrapper class details implementation is chosen at runtime, based on the Windows version. In case of Vista+, the late runtime function pointer evaluation to null - which is not seen in traces - causes the abort. --- snip --- ... 0025:Starting process L"C:\\Program Files\\ApexDC++\\ApexDC-x64.exe" (entryproc=0x140309b7c) ... 0025:Call KERNEL32.GetModuleHandleW(1403cb230 L"kernel32.dll") ret=14030f42b 0025:Ret KERNEL32.GetModuleHandleW() retval=7b820000 ret=14030f42b ... 0025:Call KERNEL32.GetProcAddress(7b820000,140377f30 "CreateThreadpoolTimer") ret=14030f52e 0025:Ret KERNEL32.GetProcAddress() retval=00000000 ret=14030f52e 0025:Call KERNEL32.GetProcAddress(7b820000,140377f48 "SetThreadpoolTimer") ret=14030f54c 0025:Ret KERNEL32.GetProcAddress() retval=00000000 ret=14030f54c 0025:Call KERNEL32.GetProcAddress(7b820000,140377f60 "WaitForThreadpoolTimerCallbacks") ret=14030f56a 0025:Ret KERNEL32.GetProcAddress() retval=00000000 ret=14030f56a 0025:Call KERNEL32.GetProcAddress(7b820000,140377f80 "CloseThreadpoolTimer") ret=14030f588 0025:Ret KERNEL32.GetProcAddress() retval=00000000 ret=14030f588 0025:Call KERNEL32.GetProcAddress(7b820000,140377f98 "CreateThreadpoolWait") ret=14030f5a6 0025:Ret KERNEL32.GetProcAddress() retval=00000000 ret=14030f5a6 0025:Call KERNEL32.GetProcAddress(7b820000,140377fb0 "SetThreadpoolWait") ret=14030f5c4 0025:Ret KERNEL32.GetProcAddress() retval=00000000 ret=14030f5c4 0025:Call KERNEL32.GetProcAddress(7b820000,140377fc8 "CloseThreadpoolWait") ret=14030f5e2 0025:Ret KERNEL32.GetProcAddress() retval=00000000 ret=14030f5e2 ... --- snip --- The first missing import needed is 'CreateThreadpoolTimer'. $ sha1sum ApexDC++_1.6.0_Setup.exe 1c39f7a6e6ca2160f13876e82070113ec69af65b ApexDC++_1.6.0_Setup.exe $ du -sh ApexDC++_1.6.0_Setup.exe 40M ApexDC++_1.6.0_Setup.exe $ wine --version wine-1.7.27-71-gfbcf77c Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37306 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|64-bit ApexDC 1.6.0 crashes |Multiple applications |on startup with Wine |trying to use Vista+ Thread |configured as Vista or |Pool Timer API crash on |higher (needs Thread Pool |startup with Wine |Timer API, |configured as Vista or |'CreateThreadpoolTimer') |higher | |('CreateThreadpoolTimer')(6 | |4-bit ApexDC 1.6.0, | |Watchtower Library 2014) --- Comment #2 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, revisiting, still present. Also encountered with Watchtower Library 2014 with Wine configured to Windows Vista. Similar approach as outlined in my comment #1, only debugging reveals what's missing at the time of crash. $ wine --version wine-1.7.34-159-g7b45103 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37306 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de --- Comment #3 from Sebastian Lackner <sebastian(a)fds-team.de> --- I would like to point out that I am currently working on a threadpool implementation, see bug https://bugs.winehq.org/show_bug.cgi?id=35192. The code is available here: https://github.com/wine-compholio/wine-staging/tree/master/patches/ntdll-Vis... Timer objects are already implemented, but wait objects are still missing, so at least ApexDC is still not happy. 0025:Call KERNEL32.GetProcAddress(7b820000,140377f98 "CreateThreadpoolWait") ret=14030f5a6 0025:Ret KERNEL32.GetProcAddress() retval=00000000 ret=14030f5a6 Nevertheless, it might be sufficient for some other applications. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37306 --- Comment #4 from Sebastian Lackner <sebastian(a)fds-team.de> --- I have just updated the patchset, and added threadpool wait object support. With that fixed ApexDC 1.6.0 starts as expected even when the wineprefix is set to Vista. It is not really a good test though, because the functions are not really called very often. When more apps expect CreateThreadpoolWait / ntdll.TpAllocWait it probably makes sense to open a new follow-up bug report for that. BTW: The problem also exists in the 32-bit version, and is not really win64 specific. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37306 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trash.kuleshidze(a)gmail.com --- Comment #5 from Anastasius Focht <focht(a)gmx.net> --- *** Bug 38259 has been marked as a duplicate of this bug. *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37306 --- Comment #6 from Sebastian Lackner <sebastian(a)fds-team.de> --- This issue should be fixed with http://source.winehq.org/git/wine.git/commit/eadd27a38a218e6ab27404d2981f3fe... and previous patches, please retest. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37306 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |eadd27a38a218e6ab27404d2981 | |f3fe521f13361 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, this is fixed by commit https://source.winehq.org/git/wine.git/commitdiff/eadd27a38a218e6ab27404d298... Thanks Sebastian --- snip --- ... 0023:Call KERNEL32.GetProcAddress(7b860000,140377f30 "CreateThreadpoolTimer") ret=14030f52e 0023:Ret KERNEL32.GetProcAddress() retval=7b866f60 ret=14030f52e 0023:Call KERNEL32.GetProcAddress(7b860000,140377f48 "SetThreadpoolTimer") ret=14030f54c 0023:Ret KERNEL32.GetProcAddress() retval=7b86e5cc ret=14030f54c 0023:Call KERNEL32.GetProcAddress(7b860000,140377f60 "WaitForThreadpoolTimerCallbacks") ret=14030f56a 0023:Ret KERNEL32.GetProcAddress() retval=7fd574a08dc8 ret=14030f56a 0023:Call KERNEL32.GetProcAddress(7b860000,140377f80 "CloseThreadpoolTimer") ret=14030f588 0023:Ret KERNEL32.GetProcAddress() retval=7fd574a08cc4 ret=14030f588 ... --- snip --- ApexDC 1.6.0 x86_64 still doesn't run but that's bug 36549 --- snip --- ... 0023:Call KERNEL32.GetProcAddress(7b860000,140376c88 "SetThreadGroupAffinity") ret=140304b0e 0023:Ret KERNEL32.GetProcAddress() retval=00000000 ret=140304b0e 0023:Call KERNEL32.GetProcAddress(7b860000,140376ca0 "GetThreadGroupAffinity") ret=140304b21 0023:Ret KERNEL32.GetProcAddress() retval=00000000 ret=140304b21 0023:Call KERNEL32.GetLastError() ret=140304bc6 0023:Ret KERNEL32.GetLastError() retval=0000007f ret=140304bc6 0023:Call ntdll.RtlPcToFileHeader(14047b018,0032f290) ret=14030c43c 0023:Ret ntdll.RtlPcToFileHeader() retval=140000000 ret=14030c43c 0023:Call KERNEL32.RaiseException(e06d7363,00000001,00000004,0032f260) ret=14030c47b 0023:trace:seh:raise_exception code=e06d7363 flags=1 addr=0x7b88c34c ip=7b88c34c tid=0023 0023:trace:seh:raise_exception info[0]=0000000019930520 0023:trace:seh:raise_exception info[1]=000000000032f2b0 0023:trace:seh:raise_exception info[2]=000000014047b018 0023:trace:seh:raise_exception info[3]=0000000140000000 0023:trace:seh:raise_exception rax=000000007b870408 rbx=000000014047b018 rcx=000000000032f040 rdx=0000000000000020 0023:trace:seh:raise_exception rsi=000000000032f260 rdi=000000000032f060 rbp=000000000032f190 rsp=000000000032f020 0023:trace:seh:raise_exception r8=0000000000000004 r9=000000000032f260 r10=0000000000000000 r11=0000003f72b8cd30 0023:trace:seh:raise_exception r12=0000000140325900 r13=0000000000000000 r14=0000000000000000 r15=000000000032f600 --- snip --- $ wine --version wine-1.7.46-193-g8b566b1 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37306 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #8 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.7.47. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37306 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |slifeleaf(a)gmail.com --- Comment #9 from Anastasius Focht <focht(a)gmx.net> --- *** Bug 38896 has been marked as a duplicate of this bug. *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37306 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |h.henoch(a)isc84.org --- Comment #10 from Anastasius Focht <focht(a)gmx.net> --- *** Bug 39503 has been marked as a duplicate of this bug. *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37306 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL|http://www.apexdc.net/downl |https://web.archive.org/web |oad/ |/20211128204429/https://pil | |otfiber.dl.sourceforge.net/ | |project/apexdc/ApexDC%2B%2B | |/1.6.0/ApexDC%2B%2B_1.6.0_S | |etup.exe -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla