7.3.4.2 64 bit Windows 10 Crashes When Sliding Right Scroll Bar

Calc crashes frequently when I slide the right scroll bar. I have all the latest W10 updates as of 7/21/22. It did not crash like this before the last updates by either LibreOffice or W10. I am not sure which is causing the issues. I have setup everything in Windows Defender properly when first installed but this just started. I reinstalled LibreOffce but it keeps happendng.

Erste Schritte

Bitte mal Schritt 5 im Link ausprobieren. Danke.


Sorry, my mind was probably somewhere else

First steps

Please try step 5 in the link. Thank you.

1 Like

After more research, I find that if I use the slide too bar then Calc crashes but if I click on the left or right arrow it does not crash. This really needs to be checked out.

I did not understand the other post as I only speak English.

If you had clicked the link that @Hrbrgr gave you would have seen “English”, clicking on that link would have taken you to First steps to take before submitting a bug - The Document Foundation Wiki

He suggested looking at Step 5 (Skia) first

1 Like

Thanks! This seems to be working. I appreciate the tip about clicking on the English translation as well!

1 Like

Unwilling to start new thread, I have exactly the same issue. [24.8.0.3 (X86_64) ( build 0bdf1299c94fe897b119f97f3c613e9dca6be583 )] running WIN11pro, on multiple user profiles. Since updating the new version (some weeks?) when I’m in long Writer documents, it takes awhile to “scroll” through the document vertically using right hand scroll bar. I’ve found that about half way down (about 3 seconds of scrolling) LibreOffice disappears. Poof, gone, my desktop is empty. On restart, the documents are recovered. I can’t pinpoint if it’s my cursor slipping to one side or the other (obviously because the scroll bar is only slightly wider than the point of the cursor) or what the cause might be. Just hugely annoying, it happens several times a day, easily. Why we switched to the nearly invisible thin scroll bar I’ve never understood. Auto hide is cool. But I just wanted to point out for me at least this is a very real problem. I’ve shifted my editing habits to click on “save” every minute or two, because at any time, the document could just disappear and auto-recover is not foolproof I discovered. So this post was just to see if I’m the only one.

Are you sure, that using 24.8.0.3 is OK for discussion of its failures, when the 24.8 branch already had two bugfix releases (24.8.1 and 24.8.2), and the third is being prepared (available on the main download page, at the bottom, as a prerelease version)? The bugfix releases are, well, to fix bugs. And the 0 is the very initial release, expected to improve by the following releases fast.

1 Like

I did not verify that. I want to use LibreOffice 6.0, which is on all my normal machines, but for some database thing (redraw bugs with WIN11 you know, yah, those were driving me mad) I installed what I thought was the latest and greatest LibreOffice because WIN11 is here to stay we have to adapt or die. I hoped that the later version of LibreOffice might help me avoid some of the visual overlapping aberrations. No luck, no change. I’ve no time to hack the visual stuff. I did not research to see that it was an early adoption thing that I was installing, so I deserved it.

In any case I’m a die hard LibreOfice guy, you can delete my post if desired I will not be in the slightest offended after all I did not do my research apparently. In theory I can go back and fix my own post, but that’s expecting a lot of me if I do say so myself. And LibreOffice crashing every 2 hours is driving me out of my mind because it’s a 25 minute recovery every single time. And it’s not just the scroll bar, but I haven’t been able to pinpoint the problem further than that, it’s only recently that I’ve begun to track other problems with it. It takes repetition. Or you could just leave the post, it has some info that the scroll bar was my best guess at the issue, I at least tried to provide insight right? The problem and evidence isn’t enough for a bug report. However we all need feedback, otherwise how can we progress? So that was the point of the post, it wasn’t a complaint as such. I apologize for any hassles. Thank you for what you do for the Document Foundation. R/Kevin PS on your recommendation I will update my 24.8 version. Thank you again.

~WRD0000.jpg

LibreOffice 6 can use OpenGL for rendering but there was a deny list for some graphics cards. My integrated graphics card was on it but I didn’t realise it.

For version 7 and above, OpenGL was replaced by Skia. If your graphics card was not able to use OpenGL then probably it can’t use Skia either.

In the menu, click Tools - Options - LibreOffice - View and tick the box Force Skia software rendering, allow LibreOffice to restart. Has the crash on scrolling issue going away?

I tried the Sika rendering and not, both, and did not notice a change. The deal is WIN11 screen resolution can be magnified, screen resolution independent of the “dpi” settings that have been used since WINXP → WIN10. So to get my monitor to not display microscopic font, nor huge font, I had to adjust the WIN11 monitor magnification, there was no other option. WIN11 defaults to different visual sizing than any previous windows version. We didn’t see that coming, right? Wrong. It was expected. When running LibreOffice macros, I had specifically set screen resolution settings for the display of the forms etc. Which worked for decades. Doubtless you’re familiar with it. But those settings, now combined with MS’s new graphics crapability, combine in a way that defaults a lot of my Base form controls to overlap the output of the forms etc. So I can’t use my forms controls, they’re behind the output. I can live with it, it is not a bug, it is not something I even complain about, because I was the one who adjusted the WIN11 screen magnification, and there was no way to live with the monitor resolution without that change. It drives me crazy to see how hard the Document Foundation is trying to get their software and macros to be identical to Microsofts’. Much of MS’s code practice and products are trash to begin with, and Microsoft will always break Open Software, because that’s what they’ve made a business doing since their inception. So it’s not a game of catch up, it’s a game of abandoning the only thing we had going for us to begin with. But that’s life, I get it. So that’s why all my other machines run LibreOffice 6.0. And that’s my screen resolution problems, which are provided intentionally by Microsoft. It’s not anything I can fix without recoding the macro resolution. But why change my macros when they work everywhere but in WIN11, and WIN11 from what I can see is just another temporary step into the cesspool that Microsoft is sliding ever deeper into. Where Microsoft goes, we will follow. I’ll fix my code when it fails to give me results, not before. Best Regards, Kevin

~WRD0000.jpg

Sorry there was to much to read. I did see screen magnification. There was a time when Windows 11 became unstable at a screen magnification of 175%, or was it above that?
Good luck with your investigations
[Edit]
Sorry, not scaling but increasing text size, see Redirecting

Thank you EarnestAI,

Per your request, my WIN11 “magnification and resolution”: scale is sat at 125%, “in between” too large and too small. Thanks for checking, I didn’t know about the magic 175%, very interesting thank you. Please don’t get wrapped around my axle with my headaches! I won’t even investigate that issue. We could hack it, and we could fix it, but the payoff is too small considering Microsoft will just change everything again. My original post was just to see if the “disappearing LibreOffice” issue, now I know it’s not just the vertical scroll bar, was just me personally (just me against the world) or not… I might be just pushing the mouse the wrong way, it might just be me. Today there’s been no poof LibreOffice is gone. Of course I’m not editing documents a thousand pages long today either. Humm. If I ever get more info will post it back - Thanks again!

~WRD0000.jpg