GNOME Bugzilla – Bug 792417
The current fix for Bug 789412 is a terrible CPU hog
Last modified: 2018-05-22 14:32:52 UTC
Created attachment 366623 [details] [review] it's a patch Even an idle Gnumeric keeps calling scg_scrollbar_config_real in an infinite loop, and it burns up my CPU with my GeForce 6150SE nForce 430 config. I propose a new patch based on what Nils Nordman wrote: https://bugzilla.gnome.org/show_bug.cgi?id=765410#c39 It works for me, but feel free to correct it if needed.
Argh. We're working around a poorly described bug in gtk+. I can see that blocking allocation calls that do not appear to change size might help, but I am having a hard time convincing myself that it really is enough. In other words, I am not confident that applying such a change won't just make a new symptom appear.
Even a non-working scrollbar WAS and would be a lot better for me than an unresponsive system with a loud cooling fan. Do you want systat/whatever logs to believe me? If y'all can fix GTK+ problems, go for it. I'm loosing hope. <rant> I really hate loosing my GTK(+) based programs one by one. Some have good Qt alternatives or the developers change to Qt by themselves (eg. Wireshark), but it's hard for a user to change applications when he has message bases or documents stored in proprietary formats. I've tried to use old versions of these applications but it's increasingly difficult. :( I've upgraded my Fedora hoping it could help with some GTK+ problems, but that only broke my old Liferea. :( </rant>
This problem has been fixed in the unstable development version. The fix will be available in the next major software release. You may need to upgrade your Linux distribution to obtain that newer version. We keep the timer, but avoid calling the gtk_adjustment_configure which can trigger an update storm.
Wrong place for the rant -- we're not gtk+ developers. We just use gtk+ because it seemed like a good idea at the time.
Thanks. That's a relief. I won't upgrade for _now_ as my patch works for me and it took me a lot a time to have it fixed and I shed some blood already. (I'd rather downgrade for the aforementioned Liferea, but that's off topic.) Just for my dnf package exclude list, I'd like to know what exactly counts as a major release. Shall I exclude gnumeric-1.12.* if I need this fix? (I was already ignored at / dropped from the _good_ places for ranting. But I'm interested in Qtmeric should that seem a good idea in the near future. :) )
We're not very good at version numbers. The last non-1.12 release was in 2012, I think. I doubt we will change major or minor until we get to 1.12.89 at which point people will starting thinking of it as a prerelease of something. While "qnumeric" would be a great pun, I think we're mostly locked in.
Fix is not working in all cases -- the original problem reappears. Reopening.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnumeric/issues/332.