-
Notifications
You must be signed in to change notification settings - Fork 155
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
Laravel memory leak with memcached #202
Comments
Hi @tolson17, sorry to hear if the issue you found with memcached. I would like to ask you a few more details to better understand the issue.
Thanks! |
@labbati Thanks for getting back to me! Sorry for the delay, here is the info: OS version: Linux fenrir 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64
what type of data is expected to be at that key? int? (very long) string? serialized json object? |
Hey @tolson17! Are you are still experiencing a segfault with the PHP tracer after upgrading to the latest version. :) |
@SammyK yes, it looks like it has been fixed! thank you so much! |
Hello, we are using the Laravel provider with the Memcached extension. When we are during a simple API request to retrieve 1 object it is causing a segmentation fault. For this request memcached would only be used for column type definitions and loaded once from memcached. We could not find anything unique with the data that is causing the issue but can provide the request data and expected response. We can also provide a core dump if needed. Let me know what information you need.
Request:
expected response:
The text was updated successfully, but these errors were encountered: