php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #59473 runTasks() segfaults when it couldn't connect after 1st call
Submitted: 2010-10-25 14:20 UTC Modified: 2011-05-15 14:41 UTC
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: angelo at at dot com Assigned: hradtke (profile)
Status: Wont fix Package: gearman (PECL)
PHP Version: 5.3.2 OS: Ubuntu 10.04
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: angelo at at dot com
New email:
PHP Version: OS:

 

 [2010-10-25 14:20 UTC] angelo at at dot com
Description:
------------
Somehow runTasks()  conflicts with knowing it couldn't 
connect from a previous call to runTasks()

Reproduce code:
---------------
$a = new GearmanClient();
$a->addServer('192.168.0.131');
$a->addTask('test', 'data');
$a->runTasks();
PHP Warning:  GearmanClient::runTasks(): gearman_connection_flush:could not connect in php shell code on line 1
// run runTasks again,
$a->runTasks();


Expected result:
----------------
same PHP warning

Actual result:
--------------
Segmentation fault

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2010-10-25 14:20 UTC] angelo at at dot com
fixed typo
 [2011-05-15 14:41 UTC] hradtke@php.net
I cannot fix this in any kind of meaningful way.  The libgearman client code is not cleaning up the task properly if the server cannot be reached.  I have created a bug report regarding this issue:
https://bugs.launchpad.net/gearmand/+bug/783141
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sat Oct 05 19:01:27 2024 UTC