Bug #51230 [Dup]: OVERLOAD using date() function with big integer, CPU 100%

From: Date: Sun, 07 Mar 2010 23:16:49 +0000
Subject: Bug #51230 [Dup]: OVERLOAD using date() function with big integer, CPU 100%
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-148377@lists.php.net to get a copy of this message
Edit report at http://bugs.php.net/bug.php?id=51230&edit=1

 ID:               51230
 User updated by:  dimitry at bansikov dot de
 Reported by:      dimitry at bansikov dot de
 Summary:          OVERLOAD using date() function with big integer, CPU
                   100%
 Status:           Duplicate
 Type:             Bug
 Package:          Date/time related
 Operating System: Debian5 64bit
 PHP Version:      5.2.13

 New Comment:

Tnx for answer.
The solution is to use php5.3? But i need php5.2 :(
My problem is different to #48851
date("Y",10000000000000000); - execution time 1 sec
date("Y",100000000000000000); - execution time 10 sec
date("Y",1000000000000000000); - execution time 100 sec

maybe can you help and say where can i fix this problem?


Previous Comments:
------------------------------------------------------------------------
[2010-03-07 19:22:56] derick@php.net

Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. 

Thank you for your interest in PHP.

Duplicate of #48851.

------------------------------------------------------------------------
[2010-03-07 19:18:41] dimitry at bansikov dot de

Description:
------------
On 64bit OS and using data() function with big integer as timestamp -
php come to overload (infinitely runtime + use CPU 100%) 
Please fix this bug, limit max timestamp as parameter.
To check on 64bit OS:  date("d.m.Y",100000000000000000);

Test script:
---------------
<? echo date("d.m.Y",100000000000000000); ?>



------------------------------------------------------------------------



-- 
Edit this bug report at http://bugs.php.net/bug.php?id=51230&edit=1


Thread (3 messages)

« previous php.bugs (#148377) next »