<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Entering a table with too many columns causing Writer to lock up"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134779#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Entering a table with too many columns causing Writer to lock up"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134779">bug 134779</a>
from <span class="vcard"><a class="email" href="mailto:csongor@halmai.hu" title="csongor@halmai.hu">csongor@halmai.hu</a>
</span></b>
<pre>I increased the page size from 21x29.7 to 600x29.7 (~30 A4 wide, the max width
of a Writer document) so that I see the result.
I created the table with 2000 columns. After a couple of seconds it has been
created. LO worked well, just slightly more slowly than usual. But it was
absolutely usable.
So limiting the number of columns to 600 is definitely something I would vote
against.
Creating a 4000x2 table was also quick but the navigation became painfully
slow.
I was able to create a 9999x2 table as well but LO was using a whole CPU core
at 100% and it was practically unusable.
So, it looks to be a performance issue, not a "doesn't work" issue.
I am not sure there is a real use case for this but if it works slowly then it
is still better than not working at all. If I create something unusually large
then an unusually slow response is acceptable.
On the other hand, I don't understand why it uses any CPU at all (beyond some
very basic usage, like <1%). If there is no user action that changes the
document then what is it calculating?
This seems to be a design flaw to me which can be very hard to fix. But fixing
that design problem would solve many performance issues of LO, not just this
edge case. So I think it would be better to figure out why LO is working after
the table has been created and fix that issue.
LO is a very versatile tool. You can use it for many-many things, not just
editing five-page-long A4 documents. So limiting its capabilities to the most
frequent use cases means we drop features that can be very valuable for some.</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>