https://bugs.documentfoundation.org/show_bug.cgi?id=158914
Telesto changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=158914
--- Comment #8 from Allen Belletti ---
Talked to the Smart Scroll author a bit. He mentioned that the tool sends
"Accessibility requests [...] in order to find out if the mouse cursor is over
an edge of a scrollable area." He also says
https://bugs.documentfoundation.org/show_bug.cgi?id=158914
--- Comment #7 from Allen Belletti ---
It turns out that @kdub is absolutely correct. I use a Logitech Marble Mouse
(the trackball) and in order to enable quick scrolling, I've been running a
little tool called "Smart Scroll"
https://bugs.documentfoundation.org/show_bug.cgi?id=158914
--- Comment #6 from kdub ---
> Mine appears identical to @kdub's except that he's using a better Mac ;-)
>
> Still looks like something about my environment must be triggering the
> behavior.
Lol, yes, our Macs are almost identical.
https://bugs.documentfoundation.org/show_bug.cgi?id=158914
--- Comment #5 from Allen Belletti ---
I'd been meaning to try the Mac/Intel build and @kdub inspired me to do so.
TBH, I really expected the issue to disappear but it did not. As far as I can
tell, it's behaving identically to the Apple
https://bugs.documentfoundation.org/show_bug.cgi?id=158914
Telesto changed:
What|Removed |Added
CC||plub...@libreoffice.org
--- Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=158914
kdub changed:
What|Removed |Added
CC||kemaldon...@csumb.edu
--- Comment #3
https://bugs.documentfoundation.org/show_bug.cgi?id=158914
--- Comment #2 from Allen Belletti ---
I installed and tested the development version just now, but it behaves
essentially the same. As soon as I've selected a new Calc document, I'm able to
leak memory at will. However, I did notice a
https://bugs.documentfoundation.org/show_bug.cgi?id=158914
--- Comment #1 from Telesto ---
FWIW: a nasty bug slipped through into 7.6.4.1 which could be -indirectly -
responsible for the leaking. You might try 24.2.0.0.beta1 to (double) check if
the issue is still occurring
