Nvidia geforce gtx 960m driver version 10.18.13.5362

#Nvidia geforce gtx 960m driver version 10.18.13.5362 windows 10#
#Nvidia geforce gtx 960m driver version 10.18.13.5362 code#

#Nvidia geforce gtx 960m driver version 10.18.13.5362 windows 10#

> If you load this site with e10s, nightly, nvidia GPU on Windows 10 РµСљвЂ 4 are

#Nvidia geforce gtx 960m driver version 10.18.13.5362 code#

Is the chromium code doing something different? From comment 0, this does not seem to work for :dvander So, I guess it is using the Intel, can I force it to the nvidia one? What do you see in the 'Adapter Description'Р”Р„dapter Description Intel(R) HD Graphics 4600Р”Р„dapter Description (GPU #2) NVIDIA Quadro K2100M Right, I guess it will be some other system call further down the stack, which is causing the actual problem. > failing at line 33 before I see any errors with the sandbox. > Created attachment 8722079 > Here's a sandbox log when running with MOZ_WIN_SANDBOX. (In reply to Mason Chang from comment #10) If you load this site with e10s, nightly, nvidia GPU on Windows 10 РµСљвЂ 4 are you crashing? From comment 0, this does not seem to work for :dvander as well. > If you set =1 and restart, does it start > one, but just looking again, maybe our job level is causing this. > I thought that our content sandbox wasn't any stronger than the chromium gpu What do you see in the 'Adapter Description' and 'WebGL Renderer'? > 4600 one, so maybe it isn't using the nvidia one. > My Windows 10 laptop has an nvidia Quadro K2100M and a built in Intel HD > (In reply to Mason Chang from comment #8) gfxInit is already failing at line 33 before I see any errors with the sandbox. Here's a sandbox log when running with MOZ_WIN_SANDBOX. > Unfortunately, there isn't any system logging of which I know. > It tends to be some sort of access denied error code, but of course > After that it's a matter of debugging / tracing through system calls. > There is a pref or you can run with env var MOZ_WIN_SANDBOX_LOGGING=1. > The only logging we have is for things that you can add sandbox policy rules > (In reply to Jeff Muizelaar from comment #7) Details (In reply to Bob Owen (:bobowen) from comment #9) If you set =1 and restart, does it start working? I thought that our content sandbox wasn't any stronger than the chromium gpu one, but just looking again, maybe our job level is causing this.

My Windows 10 laptop has an nvidia Quadro K2100M and a built in Intel HD 4600 one, so maybe it isn't using the nvidia one. > and the crash in bug 1249600 does not happen. > Laptop with an Intel HD 5500 with Windows 10, device creation is successful > From the 3 reporters, all are on nvidia GPUs on Windows 10. (In reply to Mason Chang from comment #8) Unfortunately, there isn't any system logging of which I know. It tends to be some sort of access denied error code, but of course sometimes these happen anyway. There is a pref or you can run with env var MOZ_WIN_SANDBOX_LOGGING=1.Р”Р„fter that it's a matter of debugging / tracing through system calls. The only logging we have is for things that you can add sandbox policy rules for, like file or registry access. > Bob, is there a way we can find out what the sandbox is blocking from the (In reply to Jeff Muizelaar from comment #7)