Bug #64085 [Opn->Dup]: microtime(true) undervalued

Edit report at https://bugs.php.net/bug.php?id=64085&edit=1 ID: 64085 Updated by: ab@php.net Reported by: bugzilla77 at gmail dot com Summary: microtime(true) undervalued -Status: Open +Status: Duplicate Type: Bug Package: Date/time related Operating System: Windows 7 x86/x64 PHP Version: 5.5.0alpha4 Block user comment: N Private report: N New Comment: Duplicate of bug #64370 Previous Comments: ------------------------------------------------------------------------ [2013-02-09 16:29:47] adam123 at hotmail dot com ...and the bug can be reproduced on Apache 2.4 + php5apache2_4.dll. ------------------------------------------------------------------------ [2013-02-09 16:13:26] adam123 at hotmail dot com The bug can be reproduced on Apache 2.2 + php5apache2_2.dll. ------------------------------------------------------------------------ [2013-01-28 08:54:25] bugzilla77 at gmail dot com The next evidence of the problem: microtime (true) can return 10 seconds less than the value of $_SERVER['REQUEST_TIME_FLOAT'] Do you understand this nonsense? ...that real time from microtime(true) is 10 seconds less than request time? ------------------------------------------------------------------------ [2013-01-28 08:33:03] bugzilla77 at gmail dot com Imagine that time() and microtime (true) are very similar. The difference is the type of data returned: int and float. The integer part must be the same them at the same moment. Can you imagine this obviousness? PHP 5.5 return values different by 10 seconds! PHP 5.4 will never wrong on the same machine. ------------------------------------------------------------------------ [2013-01-28 00:53:49] sixd@php.net Regardless of whether it makes sense to compare the two functions, or regardless of whatever Windows system calls the two functions expose, I'd expect time1-time2 to be negative. Please review the testcase and clarify the problem description. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=64085 -- Edit this bug report at https://bugs.php.net/bug.php?id=64085&edit=1