Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:22739
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Mime-Version: 1.0 (Apple Message framework v623)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-ID: <abbfb3de7e86eed55ac008dd6367a2cf@gravitonic.com>
Content-Transfer-Encoding: 7bit
Cc: Dmitry Stogov <dmitry@zend.com>, Andi Gutmans <andi@zend.com>
Date: Thu, 13 Apr 2006 15:44:34 -0700
To: PHP Internals <internals@lists.php.net>
Subject: Unicode conversion exceptions and memory leaks
From: andrei@gravitonic.com (Andrei Zmievski)

If you run this code in PHP 6 right now, you will get a nice memory 
leak notice.

<?php

unicode_set_error_mode(FROM_UNICODE, U_CONV_ERROR_STOP | 
U_CONV_ERROR_EXCEPTION);

$u = "< \u3844 >";
try {
     $s = (binary)$u;
} catch (UnicodeConversionException $e) {
}

?>

/homes/andrei/dev/php-src/Zend/zend_unicode.c(461) :  Freeing 
0x013FC4E4 (1 bytes), script=e.php

 From what Dmitry tells me, it is impossible to fix this with the way 
our exceptions are implemented currently. I trust him on this, but at 
the same time I think we need to do something. The conversions will be 
happening in a lot of place and being able to catch an exception, if 
one results, is an important part of the workflow. I think Dmitry 
proposed that we could re-write exceptions implementation, but also 
said that it would be a lot of work. I think we should seriously 
consider it, though.

Thoughts?

-Andrei