Hi Ron,
Indeed exception may lead to leaks in certain cases. We do try and cleanup
as much as possible but the situation you describe is hard to detect. I
will however put it on our TODO list because this case could possibly be
improved on.
Andi
At 11:54 AM 8/10/2005 +0200, Ron Korving wrot
On Wed, 10 Aug 2005, Ron Korving wrote:
> Perhaps it would require an revised garbage collection mechanism? If that's
> the case and you think it's worth investing time in, I think it would be
> something for the next major version (6).
I think it would be better not to abuse Exceptions like this
icht
news:[EMAIL PROTECTED]
> I have opened the bug #34065, but it is very hard to fix it.
>
> Thanks. Dmitry.
>
> > -Original Message-
> > From: Ron Korving [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, August 10, 2005 1:55 PM
> > To: internals@lists.
I have opened the bug #34065, but it is very hard to fix it.
Thanks. Dmitry.
> -Original Message-
> From: Ron Korving [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 10, 2005 1:55 PM
> To: internals@lists.php.net
> Subject: Re: [PHP-DEV] Re: drastic memory con
You're right, using that file to create a big piece of data was just for
demonstration purposes. In my personal case it's XML parsing. The way I read
what you just said is that this is behavior by design. But if I don't throw
Exceptions, memory usage stays constant. Throwing and catching these
exce
Hello Ron,
Wednesday, August 10, 2005, 8:47:25 AM, you wrote:
> Okay Andi, the script in this message is as simple as it gets. I used a
> syslog file to create a load of data in this case, but of course you can use
> any (text) file for this.
> #!/usr/bin/php5
>function process()
> {
>
Okay Andi, the script in this message is as simple as it gets. I used a
syslog file to create a load of data in this case, but of course you can use
any (text) file for this.
#!/usr/bin/php5
This is the output it gives me (PHP 5.0.4 btw):
40232
309528
578880
846720
1114560
1382400
1650240
19180
