[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug classpath/29263] Memory leak in VMDouble.toString()
From: |
erik at cq2 dot nl |
Subject: |
[Bug classpath/29263] Memory leak in VMDouble.toString() |
Date: |
27 Jan 2010 11:00:19 -0000 |
------- Comment #8 from erik at cq2 dot nl 2010-01-27 11:00 -------
Subject: Re: Memory leak in VMDouble.toString()
Thanks for adding an additional patch.
I wonder what it takes to get these patches applied?
I believe the code is bloating here and most of the reent stuff here
is obsolete.
Applying these patches would best be done together with some serious
refactoring. To be concrete: remove the 'optimization' for allocating
bigints as it is only making performance worse.
But if I do it, will it be applied?
Best regards,
Erik
E.J. Groeneveld
Seek You Too
twitter, skype: ejgroene
mobiel: 0624 584 029
On Wed, Jan 27, 2010 at 08:15, roland dot brand at ergon dot ch
<address@hidden> wrote:
>
>
> ------- Comment #7 from roland dot brand at ergon dot ch  2010-01-27 07:15
> -------
> Created an attachment (id=19722)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19722&action=view)
> Â --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19722&action=view)
> Additional patch for VMDouble.parseDouble()
>
> I stumbled over the same leaks in version 0.98 of classpath and fixed them
> with
> the patches in this bug report.
>
> The test in comment 5 unveiled another memory leak in VMDouble.parseDouble()
> which is called by VMDouble.toString(). Problem and solution are of the same
> kind as in the dtoa.patch above.
>
> Hope these patches will make it to the release someday.
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29263
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29263