Apache2 (mod_php) spun at 100% cpu usage.
This suggested workaround works for me. Obviously, it's a limited bandaid, but thanks for suggesting it.
Does this just crash the local process for that request or will it also cause problems for other requests? Anyone able to test this?
I usually do something like:
$id = isset($_GET['id']) ? (int) $_GET['id'] : 0;
In Windows it leaves a zombie resource putting the cpu to 100%, so it doesn't seems to be a nice thing...
- Must be one of the PHP 5.3.3 versions with the bug, where very very few web hosts are running such a recent version (5.0, 5.1 and 5.2 branches are much more common)
- Must be a 32-bit version, no bug in 64-bit
- The PHP program must try to use the input as a number