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

Stéphane Guillou (stragu) <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stephane.guillou@libreoffic
                   |                            |e.org
            Summary|Formulas disappearing and   |Some formula OLE objects
                   |shrinking, and enlarging    |lost from Writer file
                   |(steps in Comment 14)       |(white frame, no content
                   |                            |when editing them)

--- Comment #61 from Stéphane Guillou (stragu) 
<[email protected]> ---
Since LO 7.4, it is a bit easier to see which formulas have been lost, by using
Tools > Update > Update all. (It previously wouldn't remove the thumbnails)

I am removing "steps in comment 14" from the summary, because it has been
established that the embedded formula object is already missing from the
archive. It is therefore not a good test to see if the issue remains.

According to the comments and the duplicates, the issue has been reproduced in
versions up to 7.1.3.

I looked at attachments (here and duplicates) and they consistently have more
than 20 OLE objects:
- attachment 159469
- attachment 156224
- attachment 125137
- attachment 168880
- attachment 127256
- attachment 139513

I think smaller documents displaying the issue were attempts at making them
minimal by removing other data (which wouldn't fix the issue of the OLE object
not having underlying data).

So Regina might be correct in saying that it has to do with the default OLE
cache limit of 20?
However, I haven't been able to reproduce the issue from scratch, creating more
than 20 formulas.

I don't think bug 114399, bug 113900 and bug 50420 are duplicates (report are
more about changing aspect ratios, wrong content and moving formulas; no
equation disappears on updating all)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to