Closed StoneMoe closed 2 years ago
StoneMoe
commented
2 years ago Since it looks like another electron app, I tried some workaround options mentioned by https://github.com/sandboxie-plus/Sandboxie/issues/440 https://github.com/sandboxie-plus/Sandboxie/issues/310 https://github.com/sandboxie-plus/Sandboxie/issues/215 https://github.com/sandboxie-plus/Sandboxie/issues/547, but got no luck
isaak654
commented
2 years ago Could you post the exact download link of the client, please?
StoneMoe
commented
2 years ago Could you post the exact download link of the client, please?
League of Legends Tencent Edition: https://down.qq.com/lol/dltools/LOL_V4.2.5.4_FULL_0_tgod_signed.exe
this issue occured after login :(
christensennn
commented
2 years ago I have the same problem.It returns SBIE2103.Also for League of Legends Tencent Edition
isaak654
commented
2 years ago SBIE2103 indicates that a sandboxed program has requested to start a driver, and that the request was denied. Which driver is it? The exact name should be reported in the message.
However, it looks like it was added a new Client anticheat without a clear mention on the 11.10 patch notes.
StoneMoe
commented
2 years ago SBIE2103 indicates that a sandboxed program has requested to start a driver, and that the request was denied. Which driver is it? The exact name should be reported in the message.
However, it looks like it was added a new Client anticheat without a clear mention on the 11.10 patch notes.
it try to load two drivers named "ace-base" and "ace-game", which should be TenProtect(Tencent's anticheat) as I know. But these driver already in previous version of this game, and the game can be played really well even with failed driver loads and some game crash reporter pops up.
So I assume this is some sort of electron(chromium?) related issue and opened this issue :D
ameaninglessname
commented
2 years ago SBIE2103 indicates that a sandboxed program has requested to start a driver, and that the request was denied. Which driver is it? The exact name should be reported in the message.
However, it looks like it was added a new Client anticheat without a clear mention on the 11.10 patch notes.
SGuard64.exe (11864): SBIE2103 Denied attempt to load system driver 'ace-base [Easy] (StartService)' SGuard64.exe (11864): SBIE2103 Denied attempt to load system driver 'ace-game [Easy] (StartService)'
The reported messages. 👆
So, Sandboxie could not fake a "system driver" loading right now?
StoneMoe
commented
2 years ago @isaak654 what can I do for you to help investigating? I'm repairing my PC these days but will respond ASAP :D
isaak654
commented
2 years ago In order to take a log with Plus, you need to enable 'Trace Log' tab by opening 'Options' menu -> 'Trace Logging'.
Once enabled, you can reproduce your issue.
After reproducing it, just right click -> 'Copy Panel' to copy the full log and post it here:
ameaninglessname
commented
2 years ago In order to take a log with Plus, you need to enable 'Trace Log' tab by opening 'Options' menu -> 'Trace Logging'. Once enabled, you can reproduce your issue. After reproducing it, just right click -> 'Copy Panel' to copy the full log and post it here:
I am getting this: Trace Logging.txt
isaak654
commented
2 years ago This line is before the first WilError you've got when you were running Client.exe:
Client.exe (15544, 13368) - 00:34:32.072 Ipc \Sessions\1\BaseNamedObjects\TenProtect3_Share_Data_15544
As suggestion, you may apply ClosedIpcPath=\Sessions\*\BaseNamedObjects\TenProtect3_* to your sandbox and try again. If it didn't work, replace ClosedIpcPath with OpenIpcPath and try again.
In case of failure, you could try the same with other Ipc(s) references or see also Sandboxie Trace if you need more debug output with IpcTrace=ad or IpcTrace=* (A and D mean allowed+denied access, * means log everything). In case you notice a perfomance decrease, that's expected. On the Plus UI, you can find these options in Sandbox options -> Advanced Options -> Tracing tab.
Additionally, you may want to open/close Pipe paths or CLSIDs (COM classes), so If you need a brief summary of the various Resource Access settings: List of Resource Access Settings
christensennn
commented
2 years ago Has anyone successfully entered?
I tried to find the line before the first WilError and apply some paths to the sandbox options.
Unfortunately it didn't work.
isaak654
commented
2 years ago Recently it was discovered a compatibility regression that was breaking another client-server game (#1154), so you may try to downgrade to 0.9.0 and verify this.
christensennn
commented
2 years ago 
I downgraded it and tried,but still got black window and this
trace.txt
isaak654
commented
2 years ago The original author of this issue already stated here that these drivers were already blocked in previous version of this game, and that the game could be played really well even with failed driver loads and some game crash reporter.
Unfortunately I have nothing more, except debugging this issue and open/close Ipc(s) further as explained above. Additionally, you may want to open/close Pipe paths or CLSIDs (COM classes): List of Resource Access Settings
StoneMoe
commented
2 years ago I tried
OpenIpcPath=\Sessions\*\BaseNamedObjects\__COND*
OpenIpcPath=\Sessions\*\BaseNamedObjects\__IPC*and even
OpenIpcPath=\*
OpenIpcPath=\Sessions\*\BaseNamedObjects\__COND*
OpenIpcPath=\Sessions\*\BaseNamedObjects\__IPC*according to LeagueClientUxRender.exe's log before it crash
but still not work :(
with IpcTrace=* enabled, log buffer seems be flooded
I'll try some other tracing configuration later
I also found some libcef crash memdump file generated by LeagueClientUxRender.exe, I downloaded the same version pdb symbol(91.1.22+gc67b5dd+chromium-91.0.4472.124_windows32), but failed to load pdb for the memdump file. I'm not really famillar with win32 things :(
BTW I suddenly realized when the "game crash repoters" pops up in previous version of this game, is exactly at the same time as this black window appears. So I think game devs collected crash reports, decieded to ignore the crash and paint it all black :D
ameaninglessname
commented
2 years ago Would 1.0 solve this related issue?
StoneMoe
commented
2 years ago Trying to find some workaround but got no luck, both of these are not work(or I did it wrong):
--disable-gpuCreateProcessW CreateProcessA to add --disable-gpu command line for LeagureClientUxRender.exeStoneMoe
commented
2 years ago 
I also tried League of Legends North America version
which is operating by Riot Games, no TenProtect included
and got excactly same result.
So I think this is not anti-cheat related problem
Download: https://lol.secure.dyn.riotcdn.net/channels/public/x/installer/current/live.na.exe
StoneMoe
commented
2 years ago LeagueClientUxRender crash dump: 2d5c72c1-854f-4e8d-be44-4cc9cfe1a31b.zip
libcef.dll: 91.1.22+gc67b5dd+chromium-91.0.4472.124
WinDBG !analyze -v result:
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
*** WARNING: Unable to verify checksum for USER32.dll
*** WARNING: Unable to verify checksum for ole32.dll
*** WARNING: Unable to verify checksum for mf.dll
*** WARNING: Unable to verify checksum for MSVCP140.dll
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3359
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 17281
Key : Analysis.Init.CPU.mSec
Value: 1093
Key : Analysis.Init.Elapsed.mSec
Value: 487139
Key : Analysis.Memory.CommitPeak.Mb
Value: 138
Key : WER.Process.Version
Value: 11.22.406.9787
FILE_IN_CAB: 2d5c72c1-854f-4e8d-be44-4cc9cfe1a31b.dmp
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
CONTEXT: (.ecxr)
eax=00000000 ebx=00000000 ecx=02659ad5 edx=00000000 esi=5f262300 edi=0aaaf720
eip=131568fa esp=0aaaf720 ebp=0aaaf824 iopl=0 nv up ei pl nz ac po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000212
libcef+0x31a68fa:
131568fa cc int 3
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 131568fa (libcef+0x031a68fa)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 00000000
PROCESS_NAME: LeagueClientUxRender.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - { }
EXCEPTION_CODE_STR: 80000003
EXCEPTION_PARAMETER1: 00000000
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0aaaf824 13156aa6 5f281894 00ede618 5f3b4880 libcef+0x31a68fa
0aaaf83c 12414b8a 5f281880 5f51c000 00000000 libcef+0x31a6aa6
0aaaf8b8 12d62945 16f7eca8 5f51c000 12440b76 libcef+0x2464b8a
0aaaf950 12d625d5 0aaaf978 0aaaf980 00000000 libcef+0x2db2945
0aaaf9c8 1243fc5b 0aaaf9e0 5f2ed304 00000004 libcef+0x2db25d5
0aaafa18 1243f527 5f2ed2b4 ffff0000 60ce339d libcef+0x248fc5b
0aaafa34 12d63019 5f2ed2b4 00000008 ffffffff libcef+0x248f527
0aaafa70 123fba42 00000001 ffffffff 7fffffff libcef+0x2db3019
0aaafabc 12428a78 0aaafac8 1692d0cd 16deb148 libcef+0x244ba42
0aaafae4 12428c00 0aaafb00 5f201440 00000000 libcef+0x2478a78
0aaafb34 1244761a 5f28ca20 00000ac8 60ce32fd libcef+0x2478c00
0aaafb54 7737fa29 5f2899f0 7737fa10 0aaafbc0 libcef+0x249761a
0aaafb64 77a77a9e 5f2899f0 ff6a89c2 00000000 kernel32!BaseThreadInitThunk+0x19
0aaafbc0 77a77a6e ffffffff 77a98a3c 00000000 ntdll!__RtlUserThreadStart+0x2f
0aaafbd0 00000000 12447560 5f2899f0 00000000 ntdll!_RtlUserThreadStart+0x1b
SYMBOL_NAME: libcef+31a68fa
MODULE_NAME: libcef
IMAGE_NAME: libcef.dll
STACK_COMMAND: ~49s ; .ecxr ; kb
FAILURE_BUCKET_ID: BREAKPOINT_80000003_libcef.dll!Unknown
OSPLATFORM_TYPE: x86
OSNAME: Windows 10
IMAGE_VERSION: 91.1.22.0
FAILURE_ID_HASH: {12df79a2-4c27-85df-b85c-2bc318e11fa3}
Followup: MachineOwner
---------
https://github.com/sandboxie-plus/Sandboxie/releases/tag/1.0.8 League of Legends is correctly running with latest version.
Thanks!
StoneMoe
commented
2 years ago https://github.com/sandboxie-plus/Sandboxie/releases/tag/1.0.8 League of Legends is correctly running with latest version.
Thanks for informing, I did more tests: Plus x64 0.9.8d: not work Plus x64 1.0.2: not work Plus x64 1.0.3: works Plus x64 1.0.8: works
since Chromium HW acceleration issue is resolved in v1.0.3, I think it's related. huge thanks to developers actively maintaining!!
R0uli078
commented
2 years ago Hi ! It still doesn't work for me when I lauch a game. Only the Lol Client work.
StoneMoe
commented
2 years ago NOTICE: Tencent will ban your account for a month if you run LOL in sandbox for "game client modification"
ameaninglessname
commented
2 years ago NOTICE: Tencent will ban your account for a month if you run LOL in sandbox for "game client modification"
Haven't experience it yet, i didn't play it within one or two week, version updated?
Describe the bug League of Legends matchmaking client window is totally black.
To Reproduce Steps to reproduce the behavior:
debug.logExpected behavior It works well.
Screenshots
System details and installed software:
Additional context Previous game version works well, got this issue after upgrading to latest game version.
Game log logs in
LeagueClient\debug.log, which is wrote byLeagueClientUx.exe/LeagueClientUxRender.exe