[Libreoffice-bugs] [Bug 138494] Crash on FILEOPEN with very large table feature enabled

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=138494

Michael Weghorn <m.weghorn at posteo.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO
     Ever confirmed|0                           |1

--- Comment #3 from Michael Weghorn <m.weghorn at posteo.de> ---
(In reply to Ralf Habacker from comment #0)
> After I enabled experimental feature support and support for very large
> tables, LO now crashes when opening the same file.

Looking at the backtraces, I'm wondering whether those problems are directly
related to the file or rather other features that were enabled as well by the
"experimental" switch. (The second bt e.g. looks related to extension manager.)

Does everything work reproducibly as expected if you use a different file (and
reliably produce the same backtraces when you use the problematic file)?

> Following the hints of the mentioned bug to track this problem, I received a
> first trace with 
> 
> localc --backtrace <file>
> 
> Since the crash was caused by a termination signal indicating a C++
> exception, I followed the hints for catching exceptions and got an
> additional trace, which is also attached.

Out of curiosity: Where do I find those hints?

> Unfortunately I cannot attach the file in question here for data protection
> reasons. But I can do further tests if that helps.  I could also build and
> test a local version of libreoffice 7.0.1.3 using
> https://build.opensuse.org/package/show/LibreOffice:7.0/libreoffice.

Having a way to reproduce a crash makes it much more likely that somebody will
be able to find (and fix) the underlying issue, so it'd be great if you could
find a way to either remove non-public information or create a new file that
shows the same issue.
What I usually do to find out what causes such problems is to create a copy of
the problematic file and then delete content until the problem disappears, to
strip the file down to the relevant part (which also often makes it possible to
create a new file that has the same relevant characteristic to trigger the
problem).

(I probably won't be able to help much with the issue concerning large tables
itself, but suppose that it's currently experimental for a reason.)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20201126/20620c32/attachment.htm>