Enabling CSS optimization leads to "The connection was reset" in non-core themes [#752592]

What are the steps required to reproduce the bug?
I just enable "Optimize CSS files" in Performance page.

What behavior were you expecting?
I just expected CSS files optimized!

What happened instead?
Then every non-core themes break and give "The connection was reset" message on browser.

What is my environment?
I run under windows using XAMPP package.

Why critical?
Because IE does not understand more than 31 stylesheet on a page; and for debuging my theme in IE I need the "CSS Optimzation" feature. without it my CSS files do not load on IE pages.

What else?
The reason is NOT php safe mode or permission on files directory.
and also take a look at this: http://drupal.org/node/445462

Comments

Comment #1

ridgerunner commented 16 July 2010 at 17:33

Title:	Enabling CSS optimization leads to "The connection was reset" in non-core themes	» Enabling CSS Optimzation leads to "The connection was reset" in non-core themes
Version:	6.17	» 6.16

Can you specify more precisely the Drupal configuration that causes the problem? i.e. Which non-core theme causes the problem? (and how was it configured?)

This sounds like it could be yet another manifestation of #444228: Optimize CSS option causes php cgi to segfault in pcre function "match".

Comment #2

pendashteh commented 5 May 2010 at 17:21

Also note that my websites (that have problem in local), do fine on the server. Just the same code and the same database works fine on a shared linux webhosting and causes problem on my local PC.

Comment #3

arlinsandbulte commented 5 June 2010 at 21:12

Version:

6.16

» 6.17

I have run into the same problem, but only on my local environment. My shared host (dreamhost) seems unaffected.
Whenever I enable "Optimize CSS files:" I can no longer reach the site. I only get an error saying "The connection was reset."
I solved the issue by following this: http://ghita.org/drupal-the-connection-was-reset.html

Local environment (where the problem occurs):
Windows XP
Wampserver: 2.0
Apache 2.2.11
PHP 5.2.11
MYSQL: 5.1.39

I was using the ZEN theme, but even after trying a core theme (Garland), I still get the same problem.

Comment #4

avpaderno

he/him

Italian

Brescia, 🇮🇹 🇪🇺

commented 6 June 2010 at 08:43

Title:

Enabling CSS Optimzation leads to "The connection was reset" in non-core themes

» Enabling CSS optimization leads to "The connection was reset" in non-core themes

Comment #5

arlinsandbulte commented 16 June 2010 at 13:27

Comment #6

thomas4019 commented 19 June 2010 at 03:53

Same problem and same temporary solution except it was on my production server. I am using the Garland theme.
Also of note was that I didn't get any errors in my Apache nor PHP logs.

Comment #7

henrijs.seso commented 19 June 2010 at 15:27

same here

Comment #8

ridgerunner commented 16 July 2010 at 17:33

Title:	Enabling CSS Optimzation leads to "The connection was reset" in non-core themes	» Enabling CSS optimization leads to "The connection was reset" in non-core themes
Version:	6.16	» 6.17

This problem is very likely another manifestation of #444228: Optimize CSS option causes php cgi to segfault in pcre function "match". The patch in post 185 of that thread fixes the issue and was committed to the drupal-6-dev branch. The fix is not in the current 6.17 release but will be included in the upcoming 6.18.

Long story short - The error is caused by a stack overflow. The Windows version of Apache has a relatively small stack size of 256KB when compared to most Linux versions (8MB stack). This is why the error shows up sooner in a Windows environment.