Crashes XAMPP installation after copying the theme

I found that The problem is that XAMPP crashes when the .info file contains a theme setting default that has more than 382 characters.
I'm not sure why that is but it's a problem because the "meta" variable is over 1000 characters.

This variable contains device/browser related tweaks. I do want to keep this as a variable because different designs may require different tweaks to browser zooming/scaling.

For now I'll just separate the meta tags (tweaks) from the scripts (browser bugfixes) in that default settings, so that I'll only have to load 320 characters for the meta tags. I'll have to get the scripts into the theme some other way, I'll probably add checkbox settings.
If anyone knows a better solution please let me know.

I'll upload a fix tonight but for now if you want to use the beta3 you can get around the problem like this:

1. Open up the .info file of Arctica AND the starter themes (whether you use them or not)
2. At the bottom, clear out the settings[meta] default setting so that it looks like this:

settings[media_queries]                     = '5'
settings[meta]                              = ''
settings[aavb_print]                        = '1'

3. Clear all caches. Otherwise the new .info files will not be loaded.

4. Now you should be able to load the theme settings page.

Strangely this problem only occurs in XAMPP and not in my NIX systems.

fixed in beta4

Problemsignatur:
  Problemereignisname:	APPCRASH
  Anwendungsname:	httpd.exe
  Anwendungsversion:	2.2.17.0
  Anwendungszeitstempel:	4cbbe9e8
  Fehlermodulname:	php5ts.dll
  Fehlermodulversion:	5.2.17.17
  Fehlermodulzeitstempel:	4d25fb49
  Ausnahmecode:	c00000fd
  Ausnahmeoffset:	00158843
  Betriebsystemversion:	6.1.7601.2.1.0.768.3
  Gebietsschema-ID:	1031
  Zusatzinformation 1:	98df
  Zusatzinformation 2:	98df337f4c3b9e822abbfa0468fb8d62
  Zusatzinformation 3:	bbd7
  Zusatzinformation 4:	bbd787e77e10a27826d27a98ee586b8a

Above is the signature of the crash I get everytime I try to put this theme into the folder. I am using Aquias Development Stack btw.

Apache error log shows this for my various trials:

[Tue Dec 20 19:19:44 2011] [notice] Server built: Oct 18 2010 01:58:12
[Tue Dec 20 19:19:44 2011] [notice] Parent: Created child process 2724
[Tue Dec 20 19:19:45 2011] [notice] Child 2724: Child process is running
[Tue Dec 20 19:19:45 2011] [notice] Child 2724: Acquired the start mutex.
[Tue Dec 20 19:19:45 2011] [notice] Child 2724: Starting 250 worker threads.
[Tue Dec 20 19:19:45 2011] [notice] Child 2724: Starting thread to listen on port 8082.
[Tue Dec 20 19:22:43 2011] [notice] Parent: child process exited with status 3221225725 -- Restarting.
[Tue Dec 20 19:22:49 2011] [notice] Apache/2.2.17 (Win32) PHP/5.2.17 configured -- resuming normal operations
[Tue Dec 20 19:22:49 2011] [notice] Server built: Oct 18 2010 01:58:12
[Tue Dec 20 19:22:49 2011] [notice] Parent: Created child process 7716
[Tue Dec 20 19:22:51 2011] [notice] Child 7716: Child process is running
[Tue Dec 20 19:22:51 2011] [notice] Child 7716: Acquired the start mutex.
[Tue Dec 20 19:22:51 2011] [notice] Child 7716: Starting 250 worker threads.
[Tue Dec 20 19:22:51 2011] [notice] Child 7716: Starting thread to listen on port 8082.
[Tue Dec 20 19:24:09 2011] [notice] Parent: child process exited with status 3221225725 -- Restarting.
[Tue Dec 20 19:24:23 2011] [notice] Apache/2.2.17 (Win32) PHP/5.2.17 configured -- resuming normal operations
[Tue Dec 20 19:24:23 2011] [notice] Server built: Oct 18 2010 01:58:12
[Tue Dec 20 19:24:23 2011] [notice] Parent: Created child process 4276
[Tue Dec 20 19:24:25 2011] [notice] Child 4276: Child process is running
[Tue Dec 20 19:24:25 2011] [notice] Child 4276: Acquired the start mutex.
[Tue Dec 20 19:24:25 2011] [notice] Child 4276: Starting 250 worker threads.
[Tue Dec 20 19:24:25 2011] [notice] Child 4276: Starting thread to listen on port 8082.
[Tue Dec 20 19:33:26 2011] [notice] Parent: child process exited with status 3221225725 -- Restarting.
[Tue Dec 20 19:33:33 2011] [notice] Apache/2.2.17 (Win32) PHP/5.2.17 configured -- resuming normal operations
[Tue Dec 20 19:33:33 2011] [notice] Server built: Oct 18 2010 01:58:12
[Tue Dec 20 19:33:33 2011] [notice] Parent: Created child process 7384
[Tue Dec 20 19:33:35 2011] [notice] Child 7384: Child process is running
[Tue Dec 20 19:33:35 2011] [notice] Child 7384: Acquired the start mutex.
[Tue Dec 20 19:33:35 2011] [notice] Child 7384: Starting 250 worker threads.
[Tue Dec 20 19:33:35 2011] [notice] Child 7384: Starting thread to listen on port 8082.
[Tue Dec 20 19:35:00 2011] [notice] Parent: child process exited with status 3221225725 -- Restarting.
[Tue Dec 20 19:35:07 2011] [notice] Apache/2.2.17 (Win32) PHP/5.2.17 configured -- resuming normal operations
[Tue Dec 20 19:35:07 2011] [notice] Server built: Oct 18 2010 01:58:12
[Tue Dec 20 19:35:07 2011] [notice] Parent: Created child process 7176
[Tue Dec 20 19:35:09 2011] [notice] Child 7176: Child process is running
[Tue Dec 20 19:35:09 2011] [notice] Child 7176: Acquired the start mutex.
[Tue Dec 20 19:35:09 2011] [notice] Child 7176: Starting 250 worker threads.
[Tue Dec 20 19:35:09 2011] [notice] Child 7176: Starting thread to listen on port 8082.
[Tue Dec 20 19:36:56 2011] [notice] Apache/2.2.17 (Win32) PHP/5.2.17 configured -- resuming normal operations
[Tue Dec 20 19:36:56 2011] [notice] Server built: Oct 18 2010 01:58:12
[Tue Dec 20 19:36:56 2011] [notice] Parent: Created child process 7776
[Tue Dec 20 19:36:57 2011] [notice] Child 7776: Child process is running
[Tue Dec 20 19:36:57 2011] [notice] Child 7776: Acquired the start mutex.
[Tue Dec 20 19:36:57 2011] [notice] Child 7776: Starting 250 worker threads.
[Tue Dec 20 19:36:58 2011] [notice] Child 7776: Starting thread to listen on port 8082.
[Tue Dec 20 19:37:12 2011] [notice] Parent: child process exited with status 3221225725 -- Restarting.
[Tue Dec 20 19:37:19 2011] [notice] Apache/2.2.17 (Win32) PHP/5.2.17 configured -- resuming normal operations
[Tue Dec 20 19:37:19 2011] [notice] Server built: Oct 18 2010 01:58:12
[Tue Dec 20 19:37:19 2011] [notice] Parent: Created child process 2176
[Tue Dec 20 19:37:21 2011] [notice] Child 2176: Child process is running
[Tue Dec 20 19:37:21 2011] [notice] Child 2176: Acquired the start mutex.
[Tue Dec 20 19:37:21 2011] [notice] Child 2176: Starting 250 worker threads.
[Tue Dec 20 19:37:21 2011] [notice] Child 2176: Starting thread to listen on port 8082.
[Tue Dec 20 19:39:34 2011] [notice] Apache/2.2.17 (Win32) PHP/5.2.17 configured -- resuming normal operations
[Tue Dec 20 19:39:34 2011] [notice] Server built: Oct 18 2010 01:58:12
[Tue Dec 20 19:39:34 2011] [notice] Parent: Created child process 6156
[Tue Dec 20 19:39:35 2011] [notice] Child 6156: Child process is running
[Tue Dec 20 19:39:35 2011] [notice] Child 6156: Acquired the start mutex.
[Tue Dec 20 19:39:35 2011] [notice] Child 6156: Starting 250 worker threads.
[Tue Dec 20 19:39:35 2011] [notice] Child 6156: Starting thread to listen on port 8082.

I have not yet tested on a completely vanilla install. The current sites all had various other themes in the folder but as far as I understand this complex this shouldn't cause problems.

narf...

Just confirmed with another install (multisite). This time I did put the theme into a dedicated themes folder just for one of the sites and only this site crashes. The other sites remain unharmed. The crash appears when I try to load the "Appearance" settings. I am going to investigate further...

Hi dave, very strange, I'll bet it's because of the .info file again.
Are you also on windows?

Yup. I am using the Acquia xAMP stack. Planing on digging into it this afternoon.

First finding: Definitely something with the info file. Deleting all three info files prevents crashing. Now to find the cause in the files...

gr........

Ok, something is broken with the settings[meta] line. Deleting this line entirely prevents the crash. Dunno what is the problem exactly though...

btw: Same problem exists with Tundra. Tundra causes a crash and after deletion of the bogus line in the info file(s) the theme appears on the appearance/list page without crashing Apache.

Edit: The settings[meta] line is presented in one long line. I changed it to look like the same entry in TouchPro which didn't help. But deleting any part like <meta http-equiv="cleartype" content ="on"> prevents the crash. Note that this part in TouchPro does NOT cause a crash...

Hi, I tried to fix this earlier in this thread by reducing the meta setting to less characters, and now it appears it has to be even smaller. This is really annoying because I don't want to remove any more meta tags from the default settings. I'm not sure how to fix this, maybe I'll have to write a custom function just to replace this single settings default.

Hello,

In all .info files ( 3 )

replace

settings[meta] = '

with

settings[meta] = ''

Re: #12

Replacing the single quote with the double quote for the settings[meta] solves the crashing problem. But it affects the integrity of settings[meta]. The "UX Tweaks" in theme settings is now empty.

The search for a correct solution continues ...

We establish the fact that the settings[meta] line in the .info file is the problem.

A fix is to break the settings[meta] into two lines, and then change the code logic to combine them.

Step 1: Break meta into meta1 and meta2 in .info file, and set meta to empty.

settings[meta1] = '<meta name="MobileOptimized" content ="width"><meta name="HandheldFriendly" content ="true"><meta name="apple-mobile-web-app-capable" content ="yes">'

settings[meta2] ='<meta http-equiv="cleartype" content ="on"><meta http-equiv="X-UA-Compatible" content ="IE =edge, chrome =1"><meta name="viewport" content ="width =device-width, initial-scale =1">'

settings[meta] =''

Note: Do this for Arctica, Arctica_starterkit, and Arctica_starterkit_bigtheme .

Step 2: In the /arctica/features/arctica-layoutkit/ directory, edit the "layoutkit-theme-settings.inc" file as follows.

$form['arctica_settings']['layout']['meta'] = array(
  '#type' => 'textarea',
  '#rows' => 3,
  '#title' => t('UX Tweaks'),
  '#default_value' => theme_get_setting("meta") . theme_get_setting("meta1") . theme_get_setting("meta2"),
  '#description' => t("Enter meta tags for improved browsing experience. These tags are loaded just after the title tag, before your other head contents."),
  '#required' => FALSE,
);

Note that the default value of meta is now the concatenation of itself, meta1 and meta2 : '#default_value' => theme_get_setting("meta") . theme_get_setting("meta1") . theme_get_setting("meta2"),

================================================

This fix solves the crash problem and maintains the integrity of the code logic.

This fix also applies to the Tundra theme which has the same problem.

There is more simple solution. It works for me:

settings[meta]                               = '<meta name="MobileOptimized" content ="width"><meta name="HandheldFriendly" content ="true"><meta name="apple-mobile-web-app-capable" content ="yes"><meta http-equiv="cleartype" content ="on"><meta http-equiv="X-UA-Compatible" content ="IE =edge, chrome =1"><meta name="viewport" content ="width =device-width, initial-scale =1">'

P.S. Don't forget to modify all 3 info-files.

The solution in #15 does not work. Nothing is changed in the settings[meta] . It's still the same long meta. It still crashes.

The solution in #14 works.

Nothing is changed in the settings[meta]

No, I've removed line breaks at the beginning and at the end of the string.

Before:

settings[meta] = '
<meta name="MobileOptimized" content ="width">...<meta name="viewport" content ="width =device-width, initial-scale =1">
'

After:

settings[meta] = '<meta name="MobileOptimized" content ="width">...<meta name="viewport" content ="width =device-width, initial-scale =1">'

And - I've checked once more - this modification makes Arctica to work for me (on WinXP-SP3, Apache 2.2.14, PHP 5.2.11).

OK, the explanation makes it clearer. Removing line breaks of the settings[meta] string solves the problem. Solution #17 works for me now on WAMP. I consider this problem now fixed.

Thx for your help guys much appreciated. I thought i had it fixed at #2 so this time i want to be sure before i create another release.

Can everyone confirm the latest dev does not crash your site? Ill leave this open til wednesday and make a release if theres no problems with the dev.

arctica-7.x-1.x-dev (December 26, 2011 - 12:01) works fine both on Win & Linux.

So why the freck isn't it working for me? Going to investigate tomorrow but atm I have no clue...

How about if you reduce the setting in the dev version to 1 meta tag? I think the number of characters might make the difference

I confirm that arctica-7.x-1.x-dev (December 26, 2011) works on WAMP and LAMP.

arctica-7.x-1.x-dev (December 26, 2011)
Don't work in wamp (64) windows ultimate

Allright that's 2 guys already that have their wamp stacks blow up, I guess I have to do some concatenation of meta tags like Pete suggested.

My dabbling around with the built from the 26th wasn't successful. I stand put to test anything new...

edit: I got a combination of Arctica, Tundra and TouchPro to NOT crash. I deleted all meta lines in the info files of the various starterkits so that only info files in the arctica, tundra and touchpro folders remained. I also had to change a lot stuff like content ="on" to content="on".

Themes seem to work ok but I am just starting to fool around now...

Can you tell me what your environment is exactly? What lamp stack and what version of windows?
It's hard for me to work this out without being able to reproduce.

I'll install the Acquia stack when I have time and see where that takes me.

W7 Home Premium (64Bit) but I am going to test on the latest version of the Acquia stack today. They upgraded Apache since the last time I checked and maybe this solves the problem.

Edit: Nope. On a vanilla install running the latest stack from Acquia all I got are crashes. The dev desktop is sporting Apache 2.2.21 and Mysql 5.1.59-community. Do you need anything else?

I can now confirm Acquia Drupal stack crashes when Arctica is added. It seems to have a smaller .info string length limit.

If you remove all contrib stuff (or start with a fresh install) and install attached theme (just Arctica core with modifications) do you have a crash?

For me this is working on the acquia-drupal stack on W7 X64. If this still crashes for you, try removing more meta tags from the .info file at line 130 until you can refresh the page without crashing. If this is in fact necessary the bug might be hardware dependent.

Working for me too.

Created issue for Tundra #1391898: Crashes Apache on Aquia Stack.

Just out of curiosity: Any plans here?

yes, this week I've not been able to work in Arctica due to time constraints. Next week I should be able to get a new release out, I hope.

Thanks for the update.

fixed in next release

You can fix this by setting the
pcre.backtrack_limit and pcre.recursion_limit lower!

you can do this in settings.php I opted to set it in my .htaccess like so:

php_value pcre.backtrack_limit 100
php_value pcre.recursion_limit 100

Added drupal version