Glossary 6.x.1.x-dev from 2009-Jan-20 causes WSOD (white screen on all pages except admin pages)

Please repair this immediately and publish a new version without this horrible problem!

Comments

drupalfan2’s picture

drupalfan2 commented
Version: 6.x-1.x-dev » 6.x-1.6

I tested and found out:

6.x-1.6 has the same problem: Causes WSOD error. All pages withou admin pages are empty, totally empty.
Please repair!

AaronCollier’s picture

AaronCollier commented
Status: Needs work » Postponed (maintainer needs more info)

Can you say more about what the problem is? What you did to find the error? There are a couple of thousand people using the module now, including me, and I'm not getting a WSOD. Is this on a fresh install or what happened?

drupalfan2’s picture

drupalfan2 commented

It is a new drupal project with many modules and with a high value for php memory limit: 96MB.

Glossary module is fully configrated and there are about 50 or 80 glossary entries. Glossary works.

But when I click on taxonomy pages (news category) or on glossary entries, then after a few clicks all taxonomy and glossary term pages are white pages (WSOD). After some time all pages exect admin pages are white without any content.

Taxonomy images are enabled but when I disable this module (only taxonomy enabled) the problem is the same.

Can you help? It is urgent.

AaronCollier’s picture

AaronCollier commented

So it happens also when you click on taxonomy terms that aren't a part of your glossaries? Can you reproduce the error on a fresh install? If not, it might be hard to diagnose from afar what is specifically causing the problem.

drupalfan2’s picture

drupalfan2 commented

I tested this glossary problem again:

Yesterday I tested and could not reproduce the problem, erverything was okay, no problems (maybe my test was to short).

Today I tested again and the error occurd after 10 or 15 minutes (turned on glossary module, turned off cache while testing).

Then I tried to find out more with the Diagnostic Tools Modules wsdo and bench_chart. No results. Both modules have a lot of problems, there are a lot of error messages (incorrect paths, etc), no hint about wsod problem, maybe the module didn't work correctly.

drupalfan2’s picture

drupalfan2 commented

After turning on glossary module on live site and turning off cache this happens:

- after 10 oder 15 minutes glossary term pages are without content (only white site, no html content, nothing, totallly empty)
- some, not all, taxonomy pages (with url aliases) from other content types (story, ..) have the same problem: No content, white site.

When I turn off glossary module all the probleme are gone, everything is okay.

How can I find out why this glossary module does not work?
Is there another way to test this?

AaronCollier’s picture

AaronCollier commented
Category: bug » support

It might be an interaction with some other module or something like that. You could work on a development site and turn off all modules except for Glossary and see if it works. The reason to try it on a new install is to see if it's something in your content or other modules that is doing it. Since no one else seems to have the problem, it seems to be somehow the interaction of what you have in your site. If you start new and it still happens, then we can investigate it more.

Also, I wouldn't recommend turning on and off modules for these kinds of tests in a live site.

AaronCollier’s picture

AaronCollier commented
Status: Postponed (maintainer needs more info) » Active
drupalfan2’s picture

drupalfan2 commented
Priority: Critical » Normal
Status: Active » Fixed

After restarting Apache the problem disappeared!!!

Why this?

drupalfan2’s picture

drupalfan2 commented

The problem occured again, because glossary module was active!!!!
What can we do?

drupalfan2’s picture

drupalfan2 commented
Priority: Normal » Critical
Status: Fixed » Active

critical

ozon’s picture

ozon commented

Hm, this modules works finde for me. After a few days use, I have not found a problem.
I use the Cherokee-Webserver ( apache smell ;) ).

drupalfan2’s picture

drupalfan2 commented
Status: Active » Fixed

After the operating system of the server has been changed to lenny (debian 5.0) and eaccelerator was replaced through apc the problem disappeared.

Maybe Apache Seg Faults have caused this problem.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

andyschm’s picture

andyschm commented
Status: Closed (fixed) » Active

Glossary module induces cache corruption in the eaccelerator extension, leading to segmentation faults ("white screen of death") after a few minutes of normal run-time.

This may not technically be considered a bug in glossary, but it is triggered by the use of non-ASCII-printable characters in the source code of glossary.module, which I think is bad coding practice even if it does pass through the PHP interpreter without complaint, it will still cause problems with source code editors and preprocessors (such as eaccelerator).

The offending characters are in function _glossary_is_boundary, which in 'less' are displayed as like so:

function _glossary_is_boundary($char) {
if (extension_loaded('mbstring')) {
return (mb_strpos("!\"#\$%&'()*+,-./:;<=>?@[\]^_`{|}~<92> <93><94> \t\n\r", $char) !== FALSE);
}
else {
return (strpos("!\"#\$%&'()*+,-./:;<=>?@[\]^_`{|}~<92> <93><94> \t\n\r", $char) !== FALSE);
}
}

I believe these sequences need to be escaped using the \x encoding for hexadecimal in strings.

See "Escaped characters" in http://www.php.net/manual/en/language.types.string.php

\x[0-9A-Fa-f]{1,2} the sequence of characters matching the regular expression is a character in hexadecimal notation

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Issue summary: View changes
Status: Active » Closed (outdated)