<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:todventtu@suomi24.fi" title="Buovjaga <todventtu@suomi24.fi>"> <span class="fn">Buovjaga</span></a>
</span> changed
<a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Editing any slide element (text, shapes, images, etc.) causes noticeable lags"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=121985">bug 121985</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<td style="text-align:right;">Ever confirmed</td>
<td>1
</td>
<td>
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Editing any slide element (text, shapes, images, etc.) causes noticeable lags"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=121985#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Editing any slide element (text, shapes, images, etc.) causes noticeable lags"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=121985">bug 121985</a>
from <span class="vcard"><a class="email" href="mailto:todventtu@suomi24.fi" title="Buovjaga <todventtu@suomi24.fi>"> <span class="fn">Buovjaga</span></a>
</span></b>
<pre>(In reply to Stefan Zurucker from <a href="show_bug.cgi?id=121985#c4">comment #4</a>)
<span class="quote">> So version 6.3 seems to fix part of the problem but not the root cause? I'm
> really sorry if I'm not of any help here... In any case, thank you for
> taking a look at this bug report! Please let me know if I can be of further
> assistance!</span >
Well, there is one thing that you could do with your 6.1.3 version, but it is a
bit complicated. It would be taking a callgrind trace that will allow
developers to see, what calls in the code are taking the most time.
The Ubuntu ppa for 6.1.3 offers debug symbol packages, which you need to
install:
<a href="https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux">https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux</a>
I checked here that the -dbgsym packages are available:
<a href="https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-6-1/+packages">https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-6-1/+packages</a>
Then you need to install the valgrind program (I guess just sudo apt-get
install valgrind).
Finally, you need to follow the steps in the section "GNU/Linux: How to get a
callgrind trace" in the debug info wiki article.
For the actions to perform, I think it would be enough just to move a single
element and then quit.
For compressing the callgrind.out. file, tar.xz seems to be the best choice (of
the commonly available compression formats).
If you want to do more for LibreOffice in general, you join us in the QA team:
<a href="https://wiki.documentfoundation.org/QA/GetInvolved">https://wiki.documentfoundation.org/QA/GetInvolved</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>