Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello,
I have activated this module, but when I clic on the configuration button, the site doesn't no more respons.
Comment | File | Size | Author |
---|---|---|---|
#12 | advagg-2612910-11-fix-css-parser.patch | 945 bytes | mikeytown2 |
#4 | advagg-2612910-4-http-timeout.patch | 2.5 KB | mikeytown2 |
Comments
Comment #2
mikeytown2 CreditAttribution: mikeytown2 commentedI'll need more info on this reported bug and how to reproduce it.
Comment #3
floown CreditAttribution: floown commentedAfter activated the module, I go by clicking on configuration button to : /admin/config/development/performance/advagg/font
But the site load without displaying the page, the loading clock is displayed continuously. After a few minutes (8 min), I have a blank page. I should point out immediately that I have a memory ceiling of 512 MB.
Thx for your help.
Comment #4
mikeytown2 CreditAttribution: mikeytown2 commentedMy guess is the request to is timing out
https://cdn.rawgit.com/bramstein/fontfaceobserver/master/package.json
Here's a patch that sets the timeout to 7 seconds.
Comment #6
mikeytown2 CreditAttribution: mikeytown2 commentedAssuming this fixed it for you. Patch from #4 was committed.
Comment #7
floown CreditAttribution: floown commentedHello,
I have apply the patch, the problem is the same : a white page after some long minutes.
Comment #8
floown CreditAttribution: floown commentedI have activate the module in another installation, without applying the patch, and the page appear this time!
Amazing…
Comment #9
Christopher Riley CreditAttribution: Christopher Riley commentedI am running into an issue also on a site that I am running for me it is timing out no matter what I set the php_timeout to.
Fatal error: Maximum execution time of 300 seconds exceeded in /home/site/public_html/sites/all/modules/contrib/advagg/advagg_font/advagg_font.module on line 190
Suggestions?
Comment #10
mikeytown2 CreditAttribution: mikeytown2 commented@cmriley
Thanks for that important info! That points to the while loop of the css parser never ending. I'll get a patch up fixing this sometime this week.
Comment #12
mikeytown2 CreditAttribution: mikeytown2 commentedFollowing patch has been committed. It should fix the reported issue.