https://bugs.documentfoundation.org/show_bug.cgi?id=154533

--- Comment #16 from V Stuart Foote <[email protected]> ---
(In reply to makedir from comment #15)
> Using HW acc and also using Skia under settings work fine, with OpenCL
> disabled. The moment you tick use OpenCL it crashes on start.

So what happens with the nVidia dGPU enabled and selected, not setting os via
control center for LibreOFfice to be a low demand user of Intel iGPU?

Otherwise seems reasonable. When Use OpenCL is checked enabled, LO does check
for OpenCL devices, if the os is reporting one or more OpenCL devices LO will
enumerate and attempt to use. The fact LO is seeing a nVidia OpenCL device
means the os is reporting it!  Hence my ping of nVidia's Optimus.

Kind of a corner case, but if you want to poke at LOs handling further you'll
need to install WinDbg and download the symbols library.  Then attach to the
soffic.bin while launching and capture the thread and stack trace.

The WiKi notes [2]  are a bit dated and don't include Win11 but essentially the
same process. Get the Win11 SDK [3]. Download the LO symbols [4] while setting
it up.  The "!Analyze" WinDbg command might help, but best to just dump the
thread and stack trace at crash with "~* kp" save the output and attach--having
the symbols helps identify the faulting calls and gives the devs a place to
start looking at the OpenCL handling logic.

=-ref-=
[1]  or toggle from false to true in profile registrymodifications.xcu "<item
oor:path="/org.openoffice.Office.Common/Misc"><prop oor:name="UseOpenCL"
oor:op="fuse"><value>false</value></prop></item>"

[2] https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
[3] https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/
[4] use this local Symbol Files path (good to keep 32bit and 64 bit symbols
apart):

CACHE*C:\symbols64;SRV*http://dev-downloads.libreoffice.org/symstore/symbols;SRV*http://msdl.microsoft.com/download/symbols

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to