Initial Pageload CSS Problem [#2020791]

First off, I wasn't sure how to title this issue... Might need a better title for finding it easier.

Updating to beta-1, I've noticed that my pages (in chrome) are randomly not displaying the styling as an anonymous user and digging into the developer tools, one of the CSS files doesn't seem to be created properly. It shows as "canceled" and upon looking at the headers, it turns out to be a 404 error. Keep in mind it's completely random so no "easy" way to replicate it. I thought it might be bundler, so I disabled it but I'm still having the problem, even after flushing all of the advagg files.

One thing I noticed is that the file in question, seems to have three underscores to the filename instead of two. Trying to go to the file (naturally) results in a 404, but even removing one of the underscores, it still results in a 404.

I can simply reload the page and everything is hunky-dory and loads just fine.

I've attached some screenshots in hopes that it might help narrow the problem...
---
If it isn't one thing, it's 5 others... :-)

Comment	File	Size	Author
#5	advagg-2020791-5-better-404.patch	6.28 KB	mikeytown2
#5
	2013-06-16_02-57-04.jpg	145.36 KB	philsward
	2013-06-16_02-56-17.jpg	160.99 KB	philsward

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

philsward CreditAttribution: philsward commented 16 June 2013 at 08:30

Playing around with it a bit more, it might very well be tied to bundler... Not 100% sure though :-/

I did receive the 404 on a file with two underscores (as opposed to the three mentioned earlier) so I'm kind of at a loss.

Comment #2

mikeytown2 CreditAttribution: mikeytown2 commented 17 June 2013 at 17:19

If there is an issue with an aggregate, beta1 now comes with some better debugging info. Go to admin/config/development/performance/advagg/info and under the "Get detailed info about an aggregate file" section paste in the file that is giving you a 404 (css__AXV...). Let me know what that shows.

Comment #3

mikeytown2 CreditAttribution: mikeytown2 commented 22 June 2013 at 06:34

Been thinking about this and I should make the info give its best effort even if not an exact match (Currently requires an exact match). Also have a setting that will log misses and all that AdvAgg knows about the miss; so that in your case you could turn on a 404 log and record what happened. Also have an extreme 404 mode where it will output a file (but not save it) as long as the 1st hash is a match.

Comment #4

philsward CreditAttribution: philsward commented 23 June 2013 at 06:59

@mikeytown2, In trying to track down some issues with a really slow site (15 - 40 second page loads) I disabled and removed advagg. Now that I have the slow issues worked out, I'll see about getting advagg put back on to try and give you some better feedback.

---

I don't know why, it might be coincidence, but it seems like every time I enable and use httprl, within a few days my site starts running crazy slow... I know that's another module, but I noticed you maintain it as well. The first time I enabled it for boost crawler. Several days later my site was running dog slow. Rolled back a bunch of stuff (including httprl) and got it smoothed out. This time I installed it for advagg and the same situation. I have no evidence of it being httprl, but it seems to be a common denominator. :-/

Comment #5

mikeytown2 CreditAttribution: mikeytown2 commented 27 June 2013 at 01:37

File	Size
advagg-2020791-5-better-404.patch	6.28 KB

I've implemented some changes with how advagg handles missing files. Let me know if this helps :)

Comment #6

philsward CreditAttribution: philsward commented 27 June 2013 at 08:40

Just installed the latest dev (26th) and I'm not seeing the problem as of yet... I didn't flush my caches after enabling and setting advagg up, so the issue might still crop up.

At this point, I have not applied the supplied patch and I am assuming it was not committed in the latest dev. If the problem does arise, I'll apply the patch and go from there. I'm wondering if either you got it fixed in the latest dev or I had some other goofy things going on to cause the issue, which I'm too ignorant to track down :-)