You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Zhe Liu <al...@gmail.com> on 2012/06/08 03:43:44 UTC
After long-running GUI testing, AOO3.4 becomes slower and slower, and
occupies more and more memory
Hi all,
This week I did some long-running GUI testing on AOO 3.4 using Java on
my iMac. After about 23 hours, the memory occupied by soffice changed
from 90MB to 600MB. And soffice became very slow.
My scenario is
1. Create new Text Document/Spreadsheet/Presentation/Drawing.
2. Input some simple text in it.
3. Save and then reopen it.
4. Repeat the above steps.
I think AOO has memory leak issue. Did we perform this kind of testing before?
--
Best Regards
>From aliuzhe@gmail.com
Re: After long-running GUI testing, AOO3.4 becomes slower and slower,
and occupies more and more memory
Posted by Xia Zhao <li...@gmail.com>.
Agree, maybe we can create memory leak improvement related features in next
major release.
2012/6/8 Oliver-Rainer Wittmann <or...@googlemail.com>
> Hi,
>
>
> On 08.06.2012 03:43, Zhe Liu wrote:
>
>> Hi all,
>> This week I did some long-running GUI testing on AOO 3.4 using Java on
>> my iMac. After about 23 hours, the memory occupied by soffice changed
>> from 90MB to 600MB. And soffice became very slow.
>> My scenario is
>> 1. Create new Text Document/Spreadsheet/**Presentation/Drawing.
>> 2. Input some simple text in it.
>> 3. Save and then reopen it.
>> 4. Repeat the above steps.
>> I think AOO has memory leak issue. Did we perform this kind of testing
>> before?
>>
>
> As far as I know we did not had such kind of tests for AOO 3.4.
> When I am remembering it correct there are certain efforts regarding
> memory leaks in the past for former versions - may be some documentation on
> it will be found in the wiki (the MediaWiki one).
>
> In order to solve this area I see it more sa little project than just a
> fix for a single issue. As you can see from the issue query, posted by Zhe
> Liu, there seems to be problems in different areas of our project.
>
> just my 2 cents,
> Oliver.
>
--
Best Regards,
Lily
"If you are not part of solution,you are part of problem"
Re: After long-running GUI testing, AOO3.4 becomes slower and slower,
and occupies more and more memory
Posted by Oliver-Rainer Wittmann <or...@googlemail.com>.
Hi,
On 08.06.2012 03:43, Zhe Liu wrote:
> Hi all,
> This week I did some long-running GUI testing on AOO 3.4 using Java on
> my iMac. After about 23 hours, the memory occupied by soffice changed
> from 90MB to 600MB. And soffice became very slow.
> My scenario is
> 1. Create new Text Document/Spreadsheet/Presentation/Drawing.
> 2. Input some simple text in it.
> 3. Save and then reopen it.
> 4. Repeat the above steps.
> I think AOO has memory leak issue. Did we perform this kind of testing before?
As far as I know we did not had such kind of tests for AOO 3.4.
When I am remembering it correct there are certain efforts regarding memory
leaks in the past for former versions - may be some documentation on it will be
found in the wiki (the MediaWiki one).
In order to solve this area I see it more sa little project than just a fix for
a single issue. As you can see from the issue query, posted by Zhe Liu, there
seems to be problems in different areas of our project.
just my 2 cents,
Oliver.
Re: After long-running GUI testing, AOO3.4 becomes slower and slower,
and occupies more and more memory
Posted by Chao Huang <ch...@gmail.com>.
I'm interesting in such kind of memory leak issue. I will try to identify
the problem case by case
2012/6/11 Zhe Liu <al...@gmail.com>
> Unfortunately，I lost Mac data and forget the iteration count.
> Fortunately, I also did the same test on Ubuntu:
> 361 iterations, 48hours, memory changed from 122644KB to 1133668KB，
> +2800KB per iteration.
>
> 2012/6/9 Rob Weir <ro...@apache.org>:
> > On Thu, Jun 7, 2012 at 9:43 PM, Zhe Liu <al...@gmail.com> wrote:
> >> Hi all,
> >> This week I did some long-running GUI testing on AOO 3.4 using Java on
> >> my iMac. After about 23 hours, the memory occupied by soffice changed
> >> from 90MB to 600MB. And soffice became very slow.
> >> My scenario is
> >> 1. Create new Text Document/Spreadsheet/Presentation/Drawing.
> >> 2. Input some simple text in it.
> >> 3. Save and then reopen it.
> >> 4. Repeat the above steps.
> >
> > How many iterations of this loop did you do in 23 hours?
> >
> > It would be good to know the average leak per iteration, i.e.,
> (600-90MB)/N == ?
> >
> > Although few end-users will use AOO like this, it is a good example of
> > what someone might do if they ran OpenOffice on the server, to
> > automate document conversions, etc. So it is important to reduce
> > memory leaks.
> >
> >> I think AOO has memory leak issue. Did we perform this kind of testing
> before?
> >
> > Not in 3.4.
> >
> >> --
> >> Best Regards
> >> From aliuzhe@gmail.com
>
>
>
> --
> Best Regards
> From aliuzhe@gmail.com
>
--
Best regards,
Chao Huang
Re: After long-running GUI testing, AOO3.4 becomes slower and slower,
and occupies more and more memory
Posted by zhangjf <zh...@apache.org>.
I don't think this is the only case to show all possible memory leaks.
Here we'd better have a base line of leaked memory number with a set
of files, a set of common use cases and a fixed loop count. By
comparing with that base line we can see the progress in that area in
the future.
zhangjf
On Mon, Jun 11, 2012 at 9:17 AM, Zhe Liu <al...@gmail.com> wrote:
> Unfortunately，I lost Mac data and forget the iteration count.
> Fortunately, I also did the same test on Ubuntu:
> 361 iterations, 48hours, memory changed from 122644KB to 1133668KB，
> +2800KB per iteration.
>
> 2012/6/9 Rob Weir <ro...@apache.org>:
>> On Thu, Jun 7, 2012 at 9:43 PM, Zhe Liu <al...@gmail.com> wrote:
>>> Hi all,
>>> This week I did some long-running GUI testing on AOO 3.4 using Java on
>>> my iMac. After about 23 hours, the memory occupied by soffice changed
>>> from 90MB to 600MB. And soffice became very slow.
>>> My scenario is
>>> 1. Create new Text Document/Spreadsheet/Presentation/Drawing.
>>> 2. Input some simple text in it.
>>> 3. Save and then reopen it.
>>> 4. Repeat the above steps.
>>
>> How many iterations of this loop did you do in 23 hours?
>>
>> It would be good to know the average leak per iteration, i.e., (600-90MB)/N == ?
>>
>> Although few end-users will use AOO like this, it is a good example of
>> what someone might do if they ran OpenOffice on the server, to
>> automate document conversions, etc. So it is important to reduce
>> memory leaks.
>>
>>> I think AOO has memory leak issue. Did we perform this kind of testing before?
>>
>> Not in 3.4.
>>
>>> --
>>> Best Regards
>>> From aliuzhe@gmail.com
>
>
>
> --
> Best Regards
> From aliuzhe@gmail.com
Re: After long-running GUI testing, AOO3.4 becomes slower and slower,
and occupies more and more memory
Posted by Zhe Liu <al...@gmail.com>.
Unfortunately，I lost Mac data and forget the iteration count.
Fortunately, I also did the same test on Ubuntu:
361 iterations, 48hours, memory changed from 122644KB to 1133668KB，
+2800KB per iteration.
2012/6/9 Rob Weir <ro...@apache.org>:
> On Thu, Jun 7, 2012 at 9:43 PM, Zhe Liu <al...@gmail.com> wrote:
>> Hi all,
>> This week I did some long-running GUI testing on AOO 3.4 using Java on
>> my iMac. After about 23 hours, the memory occupied by soffice changed
>> from 90MB to 600MB. And soffice became very slow.
>> My scenario is
>> 1. Create new Text Document/Spreadsheet/Presentation/Drawing.
>> 2. Input some simple text in it.
>> 3. Save and then reopen it.
>> 4. Repeat the above steps.
>
> How many iterations of this loop did you do in 23 hours?
>
> It would be good to know the average leak per iteration, i.e., (600-90MB)/N == ?
>
> Although few end-users will use AOO like this, it is a good example of
> what someone might do if they ran OpenOffice on the server, to
> automate document conversions, etc. So it is important to reduce
> memory leaks.
>
>> I think AOO has memory leak issue. Did we perform this kind of testing before?
>
> Not in 3.4.
>
>> --
>> Best Regards
>> From aliuzhe@gmail.com
--
Best Regards
>From aliuzhe@gmail.com
Re: After long-running GUI testing, AOO3.4 becomes slower and slower,
and occupies more and more memory
Posted by Rob Weir <ro...@apache.org>.
On Thu, Jun 7, 2012 at 9:43 PM, Zhe Liu <al...@gmail.com> wrote:
> Hi all,
> This week I did some long-running GUI testing on AOO 3.4 using Java on
> my iMac. After about 23 hours, the memory occupied by soffice changed
> from 90MB to 600MB. And soffice became very slow.
> My scenario is
> 1. Create new Text Document/Spreadsheet/Presentation/Drawing.
> 2. Input some simple text in it.
> 3. Save and then reopen it.
> 4. Repeat the above steps.
How many iterations of this loop did you do in 23 hours?
It would be good to know the average leak per iteration, i.e., (600-90MB)/N == ?
Although few end-users will use AOO like this, it is a good example of
what someone might do if they ran OpenOffice on the server, to
automate document conversions, etc. So it is important to reduce
memory leaks.
> I think AOO has memory leak issue. Did we perform this kind of testing before?
Not in 3.4.
> --
> Best Regards
> From aliuzhe@gmail.com
Re: After long-running GUI testing, AOO3.4 becomes slower and slower,
and occupies more and more memory
Posted by Herbert Duerr <hd...@apache.org>.
On 08.06.2012 09:36, Zhe Liu wrote:
> Is there some tools to track memory allocation? I can combine it with
> GUI testing. So we can gather the detail clue.
For your case maybe using Rational Purify could be an interesting
option. I personally love valgrind+memcheck too.
Herbert
Re: After long-running GUI testing, AOO3.4 becomes slower and slower,
and occupies more and more memory
Posted by Zhe Liu <al...@gmail.com>.
Is there some tools to track memory allocation? I can combine it with
GUI testing. So we can gather the detail clue.
2012/6/8 zhangjf <zh...@apache.org>:
> If you search the closed bug list, you may also find many fixed memory
> leak bugs.
>
> Memory leak is a kind of bugs but not a single straightforward
> problem. The used memory size increase usually is a combined result of
> many leaks for AOO. It needs many effort to identify the conditions to
> show different leaks, find their root cause and fix solution. I think
> it is a long term task along with the code base changes.
>
> On Fri, Jun 8, 2012 at 2:51 PM, Zhe Liu <al...@gmail.com> wrote:
>> I did a search in Bugzilla. This kind of memory leak has been
>> reported many times. It seems this issue has long history and nobody
>> resolves it.
>> https://issues.apache.org/ooo/buglist.cgi?quicksearch=memory%20leak&list_id=13129
>>
>>
>> 2012/6/8 Xia Zhao <li...@gmail.com>:
>>> Zhe,
>>>
>>> Thanks a lot for long run testing, no matter AOO/OOo did this kind of
>>> testing before(for AOO3.4, the answer is No), would you please raise defect
>>> in BugZilla to track this memory leak issue? Thanks a lot.
>>>
>>> Best regards,
>>>
>>> Lily
>>>
>>> 2012/6/8 Zhe Liu <al...@gmail.com>
>>>
>>>> Hi all,
>>>> This week I did some long-running GUI testing on AOO 3.4 using Java on
>>>> my iMac. After about 23 hours, the memory occupied by soffice changed
>>>> from 90MB to 600MB. And soffice became very slow.
>>>> My scenario is
>>>> 1. Create new Text Document/Spreadsheet/Presentation/Drawing.
>>>> 2. Input some simple text in it.
>>>> 3. Save and then reopen it.
>>>> 4. Repeat the above steps.
>>>> I think AOO has memory leak issue. Did we perform this kind of testing
>>>> before?
>>>> --
>>>> Best Regards
>>>> From aliuzhe@gmail.com
>>>>
>>
>>
>>
>> --
>> Best Regards
>> From aliuzhe@gmail.com
--
Best Regards
>From aliuzhe@gmail.com
Re: After long-running GUI testing, AOO3.4 becomes slower and slower,
and occupies more and more memory
Posted by zhangjf <zh...@apache.org>.
If you search the closed bug list, you may also find many fixed memory
leak bugs.
Memory leak is a kind of bugs but not a single straightforward
problem. The used memory size increase usually is a combined result of
many leaks for AOO. It needs many effort to identify the conditions to
show different leaks, find their root cause and fix solution. I think
it is a long term task along with the code base changes.
On Fri, Jun 8, 2012 at 2:51 PM, Zhe Liu <al...@gmail.com> wrote:
> I did a search in Bugzilla. This kind of memory leak has been
> reported many times. It seems this issue has long history and nobody
> resolves it.
> https://issues.apache.org/ooo/buglist.cgi?quicksearch=memory%20leak&list_id=13129
>
>
> 2012/6/8 Xia Zhao <li...@gmail.com>:
>> Zhe,
>>
>> Thanks a lot for long run testing, no matter AOO/OOo did this kind of
>> testing before(for AOO3.4, the answer is No), would you please raise defect
>> in BugZilla to track this memory leak issue? Thanks a lot.
>>
>> Best regards,
>>
>> Lily
>>
>> 2012/6/8 Zhe Liu <al...@gmail.com>
>>
>>> Hi all,
>>> This week I did some long-running GUI testing on AOO 3.4 using Java on
>>> my iMac. After about 23 hours, the memory occupied by soffice changed
>>> from 90MB to 600MB. And soffice became very slow.
>>> My scenario is
>>> 1. Create new Text Document/Spreadsheet/Presentation/Drawing.
>>> 2. Input some simple text in it.
>>> 3. Save and then reopen it.
>>> 4. Repeat the above steps.
>>> I think AOO has memory leak issue. Did we perform this kind of testing
>>> before?
>>> --
>>> Best Regards
>>> From aliuzhe@gmail.com
>>>
>
>
>
> --
> Best Regards
> From aliuzhe@gmail.com
Re: After long-running GUI testing, AOO3.4 becomes slower and slower,
and occupies more and more memory
Posted by Zhe Liu <al...@gmail.com>.
I did a search in Bugzilla. This kind of memory leak has been
reported many times. It seems this issue has long history and nobody
resolves it.
https://issues.apache.org/ooo/buglist.cgi?quicksearch=memory%20leak&list_id=13129
2012/6/8 Xia Zhao <li...@gmail.com>:
> Zhe,
>
> Thanks a lot for long run testing, no matter AOO/OOo did this kind of
> testing before(for AOO3.4, the answer is No), would you please raise defect
> in BugZilla to track this memory leak issue? Thanks a lot.
>
> Best regards,
>
> Lily
>
> 2012/6/8 Zhe Liu <al...@gmail.com>
>
>> Hi all,
>> This week I did some long-running GUI testing on AOO 3.4 using Java on
>> my iMac. After about 23 hours, the memory occupied by soffice changed
>> from 90MB to 600MB. And soffice became very slow.
>> My scenario is
>> 1. Create new Text Document/Spreadsheet/Presentation/Drawing.
>> 2. Input some simple text in it.
>> 3. Save and then reopen it.
>> 4. Repeat the above steps.
>> I think AOO has memory leak issue. Did we perform this kind of testing
>> before?
>> --
>> Best Regards
>> From aliuzhe@gmail.com
>>
--
Best Regards
>From aliuzhe@gmail.com
Re: After long-running GUI testing, AOO3.4 becomes slower and slower,
and occupies more and more memory
Posted by Xia Zhao <li...@gmail.com>.
Zhe,
Thanks a lot for long run testing, no matter AOO/OOo did this kind of
testing before(for AOO3.4, the answer is No), would you please raise defect
in BugZilla to track this memory leak issue? Thanks a lot.
Best regards,
Lily
2012/6/8 Zhe Liu <al...@gmail.com>
> Hi all,
> This week I did some long-running GUI testing on AOO 3.4 using Java on
> my iMac. After about 23 hours, the memory occupied by soffice changed
> from 90MB to 600MB. And soffice became very slow.
> My scenario is
> 1. Create new Text Document/Spreadsheet/Presentation/Drawing.
> 2. Input some simple text in it.
> 3. Save and then reopen it.
> 4. Repeat the above steps.
> I think AOO has memory leak issue. Did we perform this kind of testing
> before?
> --
> Best Regards
> From aliuzhe@gmail.com
>
Re: After long-running GUI testing, AOO3.4 becomes slower and slower,
and occupies more and more memory
Posted by zhangjf <zh...@apache.org>.
I have noticed that AOO 3.4 still have serious memory leaks in some
cases and will begin to do some studies. But I don't know if AOO/OOo
had suck kinds of test before.
zhangjf
On Fri, Jun 8, 2012 at 9:43 AM, Zhe Liu <al...@gmail.com> wrote:
> Hi all,
> This week I did some long-running GUI testing on AOO 3.4 using Java on
> my iMac. After about 23 hours, the memory occupied by soffice changed
> from 90MB to 600MB. And soffice became very slow.
> My scenario is
> 1. Create new Text Document/Spreadsheet/Presentation/Drawing.
> 2. Input some simple text in it.
> 3. Save and then reopen it.
> 4. Repeat the above steps.
> I think AOO has memory leak issue. Did we perform this kind of testing before?
> --
> Best Regards
> From aliuzhe@gmail.com