Please test with a clean profile, Menu/Help/Restart in Safe Mode
Some example file would be nice. And Help -> About info is appreciated too. It could be related to Skia Vulkan..
Created attachment 184124 [details] m.a.riosv: Please test with a clean profile, Menu/Help/Restart in Safe Mode
Hello, i have testet: 1. skia reactivated --> writer is running --> memory is increasing without crash (after one hour) 2. safe mode and skia activated --> memory is not increasing, the same behavior like deactivated skia Best regards Uwe
Please attach a sample file useful to reproduce the issue.
Created attachment 185358 [details] Document with problem I hope this is the same bug. Steps to reproduce: 1. Open the attachment with Skia enabled 2. Highlight 3 paragraphs of text 3. Scroll up and down continuously Expected behavior: memory usage stable Actual behavior: memory usage increases quickly during scrolling, until LibO crashes due to insufficient memory Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
NEEDINFO -> UNCONFIRMED I have provided steps to reproduce and test document for the problem Uwe seems to have described
I can't reproduce it. Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Neither without Skia. Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
More information: the problem only appears when "Force Skia software rendering" is unchecked. I don't have any driver updates for my graphics card
No reproducible with "Force Skia software rendering" Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded (In reply to Faisal from comment #10) > .... I don't have any driver updates for my graphics card Rely on Windows updates, sometimes it's not the best option. If not done, try updating from the graphics card producer.
Dear Uwe, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Uwe, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp