Bug #13490 Updated: Semaphores don't release automatically

ID: 13490 Updated by: lobbin Old Summary: Semaphores don't release automatically Reported By: m@savich.ru Old Status: Open Status: Feedback Bug Type: Semaphore related Operating System: FreeBSD 4.1.1 PHP Version: 4.0.6 New Comment: Is this reproducable on 4.1.1? Previous Comments: ------------------------------------------------------------------------ [2002-01-13 20:27:43] swm@php.net My bad. Re-opened. ------------------------------------------------------------------------ [2002-01-13 14:52:51] m@savich.ru http://www.php.net/manual/ru/function.sem-acquire.php: "After processing a request, any semaphores acquired by the process but not explicitly released will be released automatically and a warning will be generated." Therefore, it is NOT intended behaviour, because in my situation semaphores DON'T release automatically. And any failure in php script causes apache to hang up in few seconds, because semaphore is acquired by dead script and all other instances can't work. This really is bug. :-( ------------------------------------------------------------------------ [2002-01-13 08:35:48] swm@php.net This is intended behaviour. This is how semaphores work. =) Use sem_remove() to remove semaphores. ------------------------------------------------------------------------ [2001-09-28 19:03:32] m@savich.ru simplest script: <? $id = sem_get(0xff03e3); sem_acquire($id); ?> modules: './configure' '--with-apxs=/usr/local/apache/bin/apxs' '--with-mysql' '--enable-sysvsem' '--enable-sysvshm' '--enable-track-vars' '--enable-sockets' description: When i run that script for the first time, warning doesnt appear, as it is described in manual. All the other calls hang apache processes without any chance for semaphore to unlock. However, if i try such variant: <? set_time_limit(0); $id = sem_get(0xff03e3); sem_acquire($id); sleep(1); sem_release($id); ?> everything works perfectly for single calls, but when I run my crash-test, which calls the php script 200 times at once, it hangs the semaphore again and many apache processes stay frozen. I think, the reason is incorrect request finalization. ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=13490&edit=1