https://bugs.documentfoundation.org/show_bug.cgi?id=158129
Stéphane Guillou (stragu) changed:
What|Removed |Added
See Also||https://bugs.document
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
ady changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
--- Comment #24 from m...@helmutsteiner.net ---
The issue might have been fixed by a driver update. I didn't have any crash in
the last days even without the debugger activated. I will reactivate the OpenCL
option just to see if the bluesc
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
--- Comment #23 from V Stuart Foote ---
(In reply to me from comment #22)
> I set up WinDbg and was working the whole day with debugging activated but
> so far no crash. I will post again if something shows up.
>
> One thing that is vis
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
--- Comment #22 from m...@helmutsteiner.net ---
I set up WinDbg and was working the whole day with debugging activated but so
far no crash. I will post again if something shows up.
One thing that is visible is that I get hundreds of C++
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
--- Comment #21 from V Stuart Foote ---
With windbg opened and the soffice.bin attached and running, issue a windbg
console command to load the symbols ".reload /f" (it will take a while to
download).
Then continue to run soffice.bin by
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
--- Comment #20 from V Stuart Foote ---
unfortunately, as you note, that dump only shows the fault at
System32\ucrtbase.dll for the soffice.bin process.
To tease out more of the issue (still probably an errant nVidia or Intel call
with t
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
--- Comment #19 from m...@helmutsteiner.net ---
dump.ini in the LibreOffice folder doesn't really show helpful information.
This is the record from Windows Event Viewer:
Log Name: Application
Source:Application Error
Date:
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
--- Comment #18 from m...@helmutsteiner.net ---
Can I send you the LibreOffice crash reports somehow?
As I said, I don't get the bluescreen anymore, instead LibreOffice just
crashes. I guess it will be helpful for debugging the error.
--
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
--- Comment #17 from m...@helmutsteiner.net ---
skia.log:
RenderMethod: vulkan
Vendor: 0x8086
Device: 0xa7a0
API: 1.3.250
Driver: 0.405.479
DeviceType: integrated
DeviceName: Intel(R) Iris(R) Xe Graphics
Denylisted: no
--
You are receiv
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
--- Comment #16 from V Stuart Foote ---
(In reply to me from comment #15)
> Created attachment 190839 [details]
> opencl_devices.log
>
> I reenabled OpenCL restarted LibreOffice and literally a few seconds later
> everything hung + blues
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
--- Comment #15 from m...@helmutsteiner.net ---
Created attachment 190839
--> https://bugs.documentfoundation.org/attachment.cgi?id=190839&action=edit
opencl_devices.log
I reenabled OpenCL restarted LibreOffice and literally a few secon
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
--- Comment #14 from V Stuart Foote ---
Also, if you could check the Tools -> Options -> OpenCL "Allow use of OpenCL"
enabled again, and restart LO (hopefully without Bluescreen or LO crash) would
you post the text from LO's "opencl_devic
https://bugs.documentfoundation.org/show_bug.cgi?id=158129
V Stuart Foote changed:
What|Removed |Added
Blocks||97391
Summary|Bluesc
14 matches
Mail list logo
