Bug 454301 - Crash when using DateTimeZone object returned by Date::getTimezone
Crash when using DateTimeZone object returned by Date::getTimezone
Product: Fedora
Classification: Fedora
Component: php (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Joe Orton
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-07-07 11:51 EDT by Dennis P. Nikolaenko
Modified: 2009-01-09 02:51 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 02:51:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
PHP Bug Tracker 45038 None None None Never

  None (edit)
Description Dennis P. Nikolaenko 2008-07-07 11:51:24 EDT
Crash when using DateTimeZone object, previously returned by

This worked fine in PHP 5.2.5
Probably this is related to how DateTimeZone object is returned:

This code returns different results in 5.2.5 and 5.2.6

$old_tz = $d->getTimezone();
$d->setTimezone(new DateTimeZone('UTC'));
echo $old_tz->getName();

5.2.6 returns 'UTC', while 5.2.5 returns 'Asia/Novosibirsk' (my current
timezone). Having in mind how objects in PHP5 are returned, I can accept
this, but this must be documented properly and shouldn't cause crash.

Reproduce code:
$d = new DateTime();
$old_tz = $d->getTimezone();
$d->setTimezone(new DateTimeZone('UTC'));
// setDate() and setTime() may go here - just for this example to make
some sense
echo "Success";

Expected result:

Actual result:
PHP interpreter crashes
Comment 1 Joe Orton 2008-07-08 05:05:31 EDT
Thanks for the report.  I can see the bug, the reference to the timezone info is
not duplicated/refcounted internally, so the $old_tz contains a stale pointer
after the second setTimezone call and all bets are off from there on.
Comment 2 Joe Orton 2008-07-08 10:51:25 EDT
Patch submitted upstream http://article.gmane.org/gmane.comp.php.devel/51838
Comment 3 Joe Orton 2008-07-08 18:08:51 EDT
OK, this got merged to 5.2.x so will be there when 5.2.7 is out and makes it
through to an update.  

Can you work around it in the meantime?  I can do a build with the patch applied
if that helps, but it won't be worth pushing an update just for this.
Comment 4 Bug Zapper 2008-11-26 05:58:35 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Bug Zapper 2009-01-09 02:51:04 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.