Freezes in "In Progress" when uploading image, latest version

@hopelessone (and @lenker), check to see if it is even blocking the async connection for background optimization. If it does that, optimize on upload won’t work.

edit: and if you can figure out the WHY of the block, I’d be happy to try and work around it.

OK, I will ask my friend who takes care of that stuff on my server, get back to you soon with an answer..

Any news?

ahh, have to wait about a week, my dev guy is still on holiday, should be back real soon.

Same problem here with a png file. Desactivating parallel thing seems to solve the problem.

Same problem here.

@li-an and @facter:

If disabling the parallel option fixes it, try this to find out why:

Disable all plugins except EWWW IO. Upload an image, and see if it gets optimized (give it a few minutes, since it is working in the background). Or you can try optimizing one of the ones you’ve uploaded in the last few weeks.
If that works, then reactivate plugins one by one and try uploading/optimizing an image until it breaks again.

If it doesn’t work, also switch to one of the default themes to see if your theme is interfering with EWWW’s new background/parallel optimization.

If none of that works, check with your webhost to see if they have something blocking the plugin from using async requests to admin-ajax.php.

looks like the new version 1.9.4 fixes the issue before I could look into this, there is 1 small issue: when in Media it always shows “In Progress” it used to refresh it automatically, now you have to f5 or reload the page and it shows “Reduced by 1.4% (6.4 kB)”

using 35% cpu! both cores when optimizing (with disable parallel), is this normal? I think it is not sure ??

that’s a bit odd with parallel disabled, but feasible if you’ve uploaded multiple images at once.
and the other thing about the “in progress” not refreshing is the way it’s always been. That would be a bit expensive on the server to keep refreshing those constantly using AJAX.

ahh, ok i’m sure it refreshed before in 2.8.5..

It was just 1 image I uploaded as a test,
Reduced by 1.4% (6.4 kB)
Image Size: 464.43 kB
Re-optimize | JPG to PNG

I just used htop to check the server cores while optimizing the image when it hit 35% (only for a second though)

if you need wp or server access or anything tell me ??

I just tested it with 2.8.5 and looks like it optimizes the image faster, because when i clicked Media it was already optimized, so maybe you are right about not refreshing, seems like the 2.9.4 is a tad slower showing In Progress..

The 2 cores went to 50% in 2.8.5 so that must be normal when optimizing a small jpg

In 2.8.5, the images were optimized as you uploaded, so when you visited the Media Library they would already be done (but the uploads were slower).
In 2.9.x, the optimization happens in the background so that uploads don’t get slowed down. The result is that you can visit the Media Library right after uploading images, and you’ll see In Progress until it finishes.
For example, if you upload 10 images, and then visit the Media Library after they finish uploading, you’ll likely see some finished, and some not. That wasn’t even possible in 2.8.5, so you’re right that it is different behavior, but optimization should still take about the same amount of time overall.

ok, so some good news, i upgraded to 2.9.4 (again) to test parallel optimization, and it works ?? I uploaded 2 images and the cpu never went over 30% while doing both..

I did like the 2.8.5 behavior (images were optimized as you uploaded), as I’m a bit worried about fastcgi full page caching on the server, wonder if it takes the un-optimized image…?

Even if it caches the whole page, an image is a separate resource fetched separately by the user’s browser, so I don’t imagine that would be a problem.

yay, more good news ??

So i’m guessing this can be marked solved (even though i didn’t get the chance to investigate why 2.9.3 didn’t work for me..)

glad it’s working ??