https://bugs.documentfoundation.org/show_bug.cgi?id=78254
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #21 from Michael Weghorn <[email protected]> --- Created attachment 192032 --> https://bugs.documentfoundation.org/attachment.cgi?id=192032&action=edit hotspot flamegraph with gtk3 debug build (In reply to Xisco FaulĂ from comment #20) > this is fine with X11 > > Version: 7.2.0.0.alpha0+ / LibreOffice Community > Build ID: dff586735b6618d9b011823594a33287d8f7f223 > CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: x11 > Locale: en-US (en_US.UTF-8); UI: en-US > Calc: threaded > > Start: 10:21:02 PM > Stop: 22:21:30 > > Needed Time: 00:00:28 > > but it takes forever with GTK3, so it might be, it's slow when using > accessibility With current bibisect repo (i.e. a release build), this takes ~12s with gen, ~23s with gtk3 for the same build, so it seems to be "only" a factor of 2 slower now. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 96493091a80fb01c33ea9153b737fdc554de61f0 CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: x11 Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Attached is a hotspot flamegraph for gtk3 with a master debug build (after letting the macro run for a bit more than a minute), which doesn't seem to indicate that a11y is a main culprit, but rather the gtk clipboard handling (note VclGtkClipboard::setContents). (Debug builds aren't ideal for profiling of course, but this may still give an idea.) Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 3e9a700091872480dd085f0928d1d30b7d74cfd7 CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-US (en_GB.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
