https://bugs.documentfoundation.org/show_bug.cgi?id=123412
--- Comment #52 from Alex Thurgood <[email protected]> --- Probably the only way to try and find out what is going on would be to have a trace log on the FDB file - but is that even possible in an embedded Firebird context ? Disposing of the database context during an active LO session with other documents being opened and closed must happen at some time during the lifecycle of the session, otherwise the DB context would remain in RAM all of the time and potentially end up eating all of the resources. That cleanup would presumably be OS-dependent, so another way to find out would be to get LO running under the Instruments.app and see whether there were any sudden drops in RAM usage in the running soffice process. Unfortunately, running LO in Instruments.app and attempting to work normally with multiple documents is generally excruciatingly slow with anything but an uber-powerful machine. -- You are receiving this mail because: You are the assignee for the bug.
