Skip to content
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

Error during ajax image upload (Child 103 exited on signal 11) #84

Open
lukewhitmore opened this issue May 24, 2021 · 11 comments
Open

Error during ajax image upload (Child 103 exited on signal 11) #84

lukewhitmore opened this issue May 24, 2021 · 11 comments

Comments

@lukewhitmore
Copy link

Using PHP_TAG=7.4-dev-4.24.9

While trying to upload an image via http://example.docker.test:8000/media/add/image we end up getting a segfault.

Tried the same using PHP_TAG=7.4-dev-4.17.0 and we have no problem.

php_1 | 192.168.48.9 - 24/May/2021:17:44:23 +0000 "GET /index.php" 200 nginx_1 | 192.168.48.6 - - [24/May/2021:17:44:23 +0000] "GET /file/progress/1538241916?_format=json HTTP/1.1" 200 76 "http://example.docker.test:8000/media/add/image" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0" php_1 | [24-May-2021 17:44:23] WARNING: [pool www] child 103 exited on signal 11 (SIGSEGV - core dumped) after 18.804057 seconds from start

@lukewhitmore
Copy link
Author

Further to this, I can confirm that the error only occurs when the progress meter is used for the file upload form widget.

If 'throbber' is selected, the upload is fine.

@csandanov
Copy link
Member

What's your drupal versoin?

@lukewhitmore
Copy link
Author

Hi @csandanov I'm testing this on Drupal 9.1.8 at the moment

@csandanov
Copy link
Member

Could you provide steps to reproduce it from the scratch? I'm testing with vanilla Drupal 9 from the latest clean docker4drupal setup (master branch) using DRUPAL_TAG=9-7.4-4.28.14. I install drupal, enable media module, go to media/add/image and upload an image without any issues.

@lukewhitmore
Copy link
Author

lukewhitmore commented May 25, 2021

PHP_TAG=7.4-4.19.0 works fine.

It seems the update for uploadprogress from 1.0.3.1 to 1.1.3 might be causing problems.

@lukewhitmore
Copy link
Author

lukewhitmore commented May 25, 2021

Hi @csandanov just tried this with a vanilla install.

The upload works with the 'throbber', but if I switch to progress meter, it fails.

image

(via http://example.local:8000/admin/structure/media/manage/image/form-display)

@csandanov
Copy link
Member

Since the recent update uploadprogress says:

It requires the use of the Apache httpd web server with mod_php. Other web servers and PHP-FPM are not yet supported.

there's a PR to address segmentation fault php/pecl-php-uploadprogress#9

@lukewhitmore
Copy link
Author

Ah .. that makes a lot of sense! What do you think the best solution is for wodby/drupal-php @csandanov ?

@csandanov
Copy link
Member

Not use progress bar for now? Especially since it's not a default option

@lukewhitmore
Copy link
Author

That's not an option in this case unfortunately.

Is there a way use a recent tag, but pin the version of uploadprogress to 1.0.3.1 ?

@djun-kim
Copy link
Contributor

djun-kim commented Jun 4, 2021

FYI I'm experiencing this issue also, but with wodby/nginx:1.18-5.14.1, and Drupal 8.9.16. Thanks everyone for your work on this. Fingers crossed that the upstream uploadprogress patch gets applied - it's quite daunting to think about changing the form display settings for hundreds of sites.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants