-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Memory Corruption on XDebug Session #12927
Comments
Could you please try latest Phalcon? And without script to reproduce, web server config sample we can't deal what happens. |
@sergeyklay same problem on latest Phalcon. I pushed a branch to my invo project for to reproduce issue: https://github.com/tugrul/invo/commit/e72885f3a7e4dd4fc4adc573f0e327579aadcc63 Edit: You have to enter your Twitter App settings on service config. protected function initSharedTwitter()
{
// https://apps.twitter.com/
$twitter = new \Twitter\OAuth([
'key' => '...',
'secret' => '...'
]);
$twitter->setDI($this);
return $twitter;
} |
Just to you know zephir-lang/zephir@0.9.6...0.9.9 |
@tugrul Is problem appear with Zephir 0.9.9 ? |
@sergeyklay nothing changed with Zephir 0.9.9
|
Well i use phalcon 3.0.0, xdebug and php 7.0.13 and no problem at all. |
@sergeyklay and @Jurigag Note: No need to start xdebug session. I built docker image. First run the docker container.
Start nginx and php-fpm daemons in the container.
Visit following address in your web browser and login with any twitter account:
Your browser is going to redirect to Visit again the previous login url
Your browser is going to redirect to |
I tried 3.2.4 and still have this problem. There is no relation width xdebug extension. Problem occurs even xdebug extension is disabled. |
Thank you for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please feel free to either reopen this issue or open a new one. We will be more than happy to look at it again! You can read more here: https://blog.phalconphp.com/post/github-closing-old-issues |
Expected and Actual Behavior
First request does not have a problem. Following request have strange memory behavior when
xdebug session active. Sometimes trying to allocate annoying size of memory, sometimes segfaulting. This behavior is changing on restart php-fpm.
Please provide an email address to share coredump.
Backtrace
Details
The text was updated successfully, but these errors were encountered: