You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 20, 2019. It is now read-only.
I'm not sure of a reliable way to reproduce this from scratch, but for those of us that have started to experience it it is very repeatable. The same Drush command will produce the same segfault every single time.
For all of us, the problem is solved by disabling xhprof. I don't necessarily know that xhprof causes the bug (it is present in the backtrace): it's possible that this is some sort of exotic memory corruption and xhprof just happens to be the extension that breaks the camel's back. I opened an upstream issue to try to rule this out: phacility/xhprof#102
I've also never experienced this segfault on Jeff Geerling's Ubuntu base box, only on Beetbox. Possibly because xhprof isn't enabled by default on the Ubuntu box.
Proposed changes
Disable xhprof by default, just to be safe. It might or might not be a permanent fix, but it's probably not a bad idea all around. It appears that Beetbox has had problems with it in the past if you search the queue, there are better alternatives, and it appears to be marginally maintained (the maintainer claims to be supporting it but I see no commits in over 3 years): phacility/xhprof#85, phacility/xhprof#81
The text was updated successfully, but these errors were encountered:
Problem/Motivation
Multiple people on our project team have started getting segfaults when running certain Drush commands against a beetbox-based DrupalVM via SSH.
The segfaults look like this in syslog:
The coredump backtrace looks like this:
https://pastebin.com/4iVHND1G
Steps to reproduce
I'm not sure of a reliable way to reproduce this from scratch, but for those of us that have started to experience it it is very repeatable. The same Drush command will produce the same segfault every single time.
For all of us, the problem is solved by disabling xhprof. I don't necessarily know that xhprof causes the bug (it is present in the backtrace): it's possible that this is some sort of exotic memory corruption and xhprof just happens to be the extension that breaks the camel's back. I opened an upstream issue to try to rule this out: phacility/xhprof#102
I've also never experienced this segfault on Jeff Geerling's Ubuntu base box, only on Beetbox. Possibly because xhprof isn't enabled by default on the Ubuntu box.
Proposed changes
Disable xhprof by default, just to be safe. It might or might not be a permanent fix, but it's probably not a bad idea all around. It appears that Beetbox has had problems with it in the past if you search the queue, there are better alternatives, and it appears to be marginally maintained (the maintainer claims to be supporting it but I see no commits in over 3 years): phacility/xhprof#85, phacility/xhprof#81
The text was updated successfully, but these errors were encountered: