[Hang] UserKernel Not Responding

12
Comment below rating threshold, click here to show it.

Dataslave

Adjudicator

03-23-2013

I ran a few tests on UserKernel:
- Appears in the process list before the patcher window appears, seems
to be tied to the small "League of Legends" graphic that first appears
when you run the game.
- Stays running 100% of the time you're playing LoL.
- Disappears about 2 seconds after you exit the launcher.
- Although it stays in the process list while LoL is open, it never gets
CPU time after displaying the small LoL graphic.

Average resources used by UserKernel (avg over 5 trials) during its
normal lifetime.
- 19 threads
- 135 open ports
- 520 context switches
- 0.0% cpu usage
- 9.5mb memory
- 0.13s CPU time.

Here's a list of its open Files and Ports (snapshot with the launcher open):

Code:
/Applications/League of Legends.app/Contents/LOL/RADS/solutions/lol_game_client_sln/releases
/Applications/League of Legends.app/Contents/LOL/RADS/system/UserKernel.app/Contents/MacOS/UserKernel
/Applications/League of Legends.app/Contents/LOL/RADS/system/UserKernel.app/Contents/Frameworks/BugSplat.framework/Versions/A/BugSplat
/System/Library/Frameworks/ExceptionHandling.framework/Versions/A/ExceptionHandling
/System/Library/PrivateFrameworks/Librarian.framework/Versions/A/Librarian
/System/Library/Caches/com.apple.IntlDataCache.le.kbdx
/System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupport.dylib
/System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib
/System/Library/Keyboard Layouts/AppleKeyboardLayouts.bundle/Contents/Resources/AppleKeyboardLayouts-L.dat
/System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat
/Applications/League of Legends.app/Contents/LOL/RADS/system/UserKernel.app/Contents/Resources/SplashScreen.png
/Applications/League of Legends.app/Contents/LOL/RADS/system/UserKernel.app/Contents/Resources/lol.icns
/usr/share/icu/icudt49l.dat
/System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine
/private/var/folders/hj/6bc062z936z7ljbfvk_wngpm0000gn/C/com.apple.LaunchServices-036501.csstore
/System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/Resources/SArtFile.bin
/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
/System/Library/Extensions/ATIRadeonX2000GLDriver.bundle/Contents/MacOS/ATIRadeonX2000GLDriver
/System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/Resources/ArtFile.bin
/usr/lib/dyld
/private/var/db/dyld/dyld_shared_cache_i386
/dev/null
/dev/null
/dev/null
count=1, state=0x2
/Applications/League of Legends.app/Contents/LOL/RADS/rads_user_kernel.log1
RADS_USER_KERNEL_MUTEX_NAME
->0x830726c4c0e6d417
localhost:28126
localhost:58183->localhost:28126
localhost:28126->localhost:58183
localhost:58185->localhost:28126
localhost:28126->localhost:58186
localhost:28126->localhost:58185
localhost:28126->localhost:58227
Just guessing based on this information, it looks like in addition to
displaying the LoL graphic, its job is to sit around handing bugsplat
exceptions and writing them to the rads_user_kernel.log.

I'm sure we've all experienced the "Another instance of this launcher
is running. Do you want to terminate it?" window by now. Up until
today, I thought it was only caused by a UserKernel staying running
after improper application exit, or the user already having a copy of
the game open.

Today I launched the game a lot and had a little bit of success
replicating at least part of the error, but I still can't produce exact steps
to do so. Before each test, I ensured that UserKernel was not in
my process list.

Every 1 in 30 launches of LoL, give or take, UserKernel appears, spikes
to 100% and brings up the "Another instance of this launcher is running.
Do you want to terminate it?" window. I'd like to mention again that there
was no UserKernel process running at this time, so this dialog
shouldn't have appeared. Clicking Cancel kills the UserKernel
process. Clicking OK causes the CPU usage to fall to zero, and the
game launches as normal.

I am unable to reproduce the UserKernel (Not Responding)
behavior in Activity Monitor, though I have seen it happen before
(several weeks ago). I tried a lot of variations, and I even left multiple
UserKernel copies running at 100% for a few hours, but they never
hung.

You can easily reproduce the 100% CPU behavior by just launching the
game twice. The second UserKernel will spike to 100% and show the
"Another instance of this launcher is running. Do you want to terminate
it?" window. Reproducing the dialog error when the game is not already
running requires launching and existing the patcher a lot, and waiting just
long enough for the process list to clear before repeating.


Comment below rating threshold, click here to show it.

Mike4Real

Senior Member

03-24-2013

Looks like you went pretty hard with the investigating haha. I guess its as I suspected and it does just place the logo on screen. However I did not suspect that it also handled bugsplats. I suppose its not everyone having this problem with the process not responding though. I have heard of it happening to a few people but seems like it works fine for you.

I only need to have one instance of LoL open and it will be listed as not responding for the entire duration of my use of the LoL Client. I can play numerous amounts of games and it is still always listed in red in Activity Monitor. Its using a negligible amount of my CPU usually, like less than 1%, but its still reported as not responding.

Any ideas as to why the process would be not responding on my computer, but working totally fine on your system? I am running Snow Leopard 10.6.8 if that info is of any use. I suppose its not a HUGE bug, but since it was listed in red I was still concerned regardless of CPU usage, doesn't seem like intend behavior.


Comment below rating threshold, click here to show it.

Dataslave

Adjudicator

03-24-2013

Quote:
Originally Posted by Mike4Real View Post
Any ideas as to why the process would be not responding on my computer, but working totally fine on your system? I am running Snow Leopard 10.6.8 if that info is of any use. I suppose its not a HUGE bug, but since it was listed in red I was still concerned regardless of CPU usage, doesn't seem like intend behavior.
No idea, except 10.6.8, which I don't have easy access to, so can't test that.

System Specifications:
Model iMac 27-inch, Late 2009
Processor 2.8 GHz Intel Core i7
Memory 8 GB 1067 MHz DDR3
Graphics ATI Radeon HD 4850 512 MB
Software OS X 10.8.3 (12D78)


12