Description: Open LibreOffice cal or exel like sheet with a lot of stock market data. The file size is only 2.5mb, but it seems to fill gpu memory and when slowly scrolling or highlighting text it overloads the gpu memory and crash. Even when i scroll for 30 lines and save it still seems to overload. However if i use the scroll button on the side and quickly go thou noting happend only when i use the spin wheel of the mouse to slowly look at the data or highlight any. Steps to Reproduce: 1.Open any report history of the stock market in my case last month September and load a bot to check the data and export results 2.Look thou the data going down 3. Actual Results: Using third mouse button or scroll wheel and look tho the data by going down the numbers. 1 to 100 by the time i get to 30 it crashes and gpu memory full. System 2 Gb and processor normal Expected Results: Noting should have happend, should allow me to see the further data and not crash Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Using ryzen 7 5800U and RTX 3070 mobile with 16 gb system ram I can upload or provide the file that i am using.
Created attachment 183137 [details] The file that I am using, open to check the data and to export.
What LO version do you use, I suppose it's not 3.3.0. Also, do you use x86 or x86-64 (since I suppose it's not PowerPC) Last stable LO version is 7.3.6 and there's brand new 7.4.2
Hi, using Windows 11 latest release as of 19/10/22 64bit. libre office 7.4.1.2.
On pc Debian x86-64 with master sources updated today, I don't reproduce this. Could you upgrade to LO 7.4.2 + apply https://wiki.documentfoundation.org/QA/FirstSteps ?
Updated LibreOffice to 7.4.2. Got the latest windows and nvidia drivers. The office file still crashes but not on the 300 line but now on the 3000, not even saving the file will reset the memory or save it from crash.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to igor2001wilczynski from comment #1) > Created attachment 183137 [details] > The file that I am using, open to check the data and to export. I opened it, scrolled around and saved. No problem. Please copy and paste here the contents of your Help - About (LibreOffice - About on macOS) by clicking the copy button. This allows us to know more about your system. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: dbbfcb7e098c1c16f932785ef62ef7d3d819ad1a CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded
Dear igor2001wilczynski, 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 igor2001wilczynski, 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