Armin,
Do not know if his is related but there is a memory leak when using
ImageControls in dialogs. When filling a ImageControl with image data,
it eats memory and only release this memory after restarting OO.
greetz
Fernand
On 26/05/2015 14:45, armin.le.gr...@me.com wrote:
Hi Rory,
On 26.05.2015 10:37, Rory O'Farrell wrote:
On Tue, 26 May 2015 10:19:07 +0200
"armin.le.gr...@me.com" <armin.le.gr...@me.com> wrote:
Hi,
it should be http://bz.apache.org/ooo/show_bug.cgi?id=125519 which is
fixed and in master, would be a candidate for AOO412, too.
Sincerely,
alg
Thank you for the link to Bugzilla, Armin. That bug might answer the
crash problem which seems to be Windows related; as most of our Users
are using Windows that is good.
However this does not address the overall problem of the increasing
slow memory management as memory allocated and used by OO increases
when large files are processed, be they of graphics or just text file
handling. It may be that the fundamental logic underlying the file
structure and its processing will not permit of any improvement in
this (I don't know - it is currently beyond my knowledge), but often
a change in the algorithm used will allow an improvement in a program
bottleneck.
Has anyone any thoughts on that aspect?
Yes, constantly. For 32bit AOO (Windows unfortunately) the 4GB mem
quickly gets filled with modern bitmaps. The mentioned fix resolves
that by limiting used mem for loaded pics - not much else to be done
without bigger redesigns and on 32bit.
Rewrites of this aspect are surely welcome!
Sincerely,
alg
On 26.05.2015 00:28, Kay Schenk wrote:
On 05/25/2015 11:03 AM, Rory O'Farrell wrote:
There are constant reports of images going missing in OO Writer. The
problem is not consistently reproducible, but is there nevertheless.
A recent report suggests it might be memory related:
https://forum.openoffice.org/en/forum/viewtopic.php?f=7&t=41271&p=353246#p353246
It is also informative to move back along that thread for other
instances of the problem. I doubt that we can dismiss all
occurrences of this problem as "finger trouble" (i.e., improper user
usage).
Might it be time to consider increasing the maximum memory allocation
for graphics (currently 256 MB) and to review the memory management
of the suggested compilers? Also, in case the problem arises from
background processing which has not completed on shut down of OO,
ought a "please wait" flag be displayed, a flag specifically keyed to
any such background process?
In these days of large memory 256MB is a very small allocation.
Having observed OO's use of memory with large text (not graphics)
files I note that its allocation and consumption of memory is
increasingly slower as the amount of memory used by it increases. It
is most certainly not linear - I have no accurate method of deciding
if the increase in slowness is geometric or even exponential.
I found John Ha's analyses and comments back from Apr, 2014 very
informative. And, his final followup on Jun 7, 2014 certainly
indicates
the problem stems from exceeding the graphic memory limits.
I couldn't find an actual issue that directly related to this so I
will
enter one, and reference this thread. Maybe that will help raise
attention to it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
