[Libreoffice-bugs] [Bug 133503] Memory usage increases after file open/file close but not in 4.2

[bugzilla-daemon at bugs.documentfoundation.org]

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

--- Comment #4 from Telesto <telesto at surfxs.nl> ---
(In reply to Buovjaga from comment #3)
> Again, rule of thumb: "Is it catastrophic?" - no, so let's close.

To be or not to be. A bug is only a bug if "catastrophic"? So we can ignore
crashes.. mostly not ending catastrophic :-). Is it catastrophic if LibreOffice
would disappear as Openoffice did? Would human kind not survive? Or is the
world being blown apart by some asteroid, erasing humankind a catastrophic? Is
there catastrophe without any human surviving it? Was it a catastrophic for the
dinosaur to extincts.. did the have a problem with it.. What did they do to
prevent it? Why did the fail?

So 'catastrophic' no.. a bug yes, trivial likely.. however not able to asses
the scope .. this type of issue tends to cause problems if LibreOffice process
is kept alive long time.. opening and closing documents.. So now extent the
scope.. Do 500 runs opening/ saving/ closing a document.. what would the result
be?

I was able to bibisect it.. so it is at minimum not a sporadic something.. And
I personally found it an issue.. I have noticed it, bibisected, bisected it..
even if it's a crazy thing to do.

So there is a flaw.. big.. as said.. depends on user case... If it can be
prevented.. functioned better.. why not take notice.. 

Or there should be something in system requirements.. about LibreOffice is
designed for usages 5 hours a day, using maximum 30 documents of a size of 5
MB. Afterwards LibreOffice needs to closed and restarted.. image can only
inserted with resolution of 4 megapixels; and only 50 images are allowed.. [all
the limitation can be build in]

Also at the one end.. people are working on making LibreOffice work on
tables/phones (image handling).. See
https://bugs.documentfoundation.org/show_bug.cgi?id=130768
on the other hand we are doing as if memory can be used freely.. bug 130768 is
a waste of effort.. you can also say.. why should LibreOffice adapt.. blame the
phone maker.. with those silly specs.. and blame users should ask for phones
which a capable to run LibreOffice.. Another perspective: wait until a phone
gets released which can run LibreOffice.. 

So is this a HIGHEST/CRITICAL bug no of course not.. should this be tracked..
ideally yes.. As vector for memory optimizations.. Is somebody gonna do that..
No clue.. Hopes, hopes, hopes.. But closing as not a bug.. feels like ignoring
it.. or sweeping it under the carpet; of course different story if nobody can
reproduce it ..  

Or the whole discussion of what should be what worthy of 'bug' label. Similar
to the going backwards, and something being a regression (or even a bug?). But
if going backwards bugs, feels bug and can't be an improvement. How should be
called .. [i'm open for suggestions]. And is there a tracker for other stuff,
which can't be listed in the bug tracker because it misfits..

-- 
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/20200618/5c1d110d/attachment-0001.htm>