-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packet that is being freed has not been allocated, most likely this is due to freeing a gearman_task_st or other object twice #347
Comments
Does this happen all the time or just occasionally? The packet was freed twice, as the assertion says, "most likely this is do [sic] to freeing a gearman_task_st or other object twice." I want to say that this problem is due to a bug in the PHP extension, but I don't know for certain. Are you using the latest version from https://github.com/php/pecl-networking-gearman ? If so, you might want to open an issue there, especially if you can boil it down to something reproducible. Unfortunately, the PHP extension is not very actively maintained, I think, so I'm not sure how much help you might get there. If you recompile libgearman.so with If you can't fix the PHP extension (assuming that's the problem), you could edit if (gearman_is_allocated(packet) || !(packet->universal)) (or maybe flip that conditional around). But that makes me feel dirty just thinking about it and you should only do that as a last resort. The fix should really be made in the PHP extension, I think. |
just occasionally, i catch this after i checked I use php-gearman Debian package. Looks like its lastest version of pecl-networking-gearman P.S. new issue php/pecl-networking-gearman#17 (comment) |
A PHP extension developer posted their analysis and suggested a potential fix to the PHP extension code here: php/pecl-networking-gearman#12 (comment) They agreed that the problem is likely in the PHP extension, so I'm closing this issue. |
Nice work @esabol ! |
I've got error and looks it related to #68 (comment)
Could you explain please, what happened
The text was updated successfully, but these errors were encountered: