https://bz.apache.org/ooo/show_bug.cgi?id=126970
--- Comment #17 from orcmid <[email protected]> --- (In reply to John from comment #15) > Created attachment 85544 [details] > I think the Michael Meeks' LO bug report (2012) > > 47148 - image caching / management is utterly shambolic > > is relevant as it states > > > The code we've inherited that deals with image caching, swapping in, out, > > lifecycle management of images via strings, swapping in and out to documents > > etc. is broken beyond belief. > > > > This is a tracker bug to start aggregating these horrors. The LibreOffice "47148" is at https://bugs.documentfoundation.org/show_bug.cgi?id=47148. Note there that the "81378" and "99612" in the "See also" are recent. In general, there is consideration that the lifecycle management of images and their caching in an opened document is not handled properly and the way it is hacked together is not taking advantage of the UNO RTL technology for accomplishing such control. Remedy for this needs to be extended to cases where still-live material is spilled to disk. That introduces interaction with auto-recovery, dealing with shut-down cases, etc., and also cleaning up spilled files that are no longer part of a managed lifecycle. Unfortunately, this is all unsurprising. It is important for those working on AOO QA and the many community members who contribute on this matter to understand that any code solutions that are devised for LibreOffice are, even when readily adaptable to AOO, not available without their contributor's permission to incorporate under a license that is acceptable for Apache project source code. (The reverse direction does work.) Please do not quote code and substantial analysis of others in examining bug reports and repositories elsewhere for confirmation of common problems and the availability of analysis. -- You are receiving this mail because: You are the assignee for the issue.
