Since the latest menu patch (http://drupal.org/node/126128) landed, HEAD has been unusable on my local dev server. the issues start with:

notice: unserialize() [function.unserialize]: Error at offset 0 of 30 bytes in /head/includes/menu.inc on line 252.

... and ripple out. Versions of the patch up to the one in http://drupal.org/node/126128#comment-211574 didn't trigger this behavior, and it has never happened before with HEAD. I'm running PHP 5.1.6, mysql 5.0.27, and Apache 1.3.3. I'm poking now at the differences between the two versions of the menu patch to see if it's something specific that changed there, or whether there's a latent configuration problem with my machine that might have triggered this...

Comments

qazasd’s picture

qazasd commented
Version: 6.x-dev » 5.x-dev

drupal 5.2-dev (cvs update DRUPAL-5 on 3/15) had the same problem.
Blank page after updating by cvs (tag= Drupal5).Even if I changed memory_limit=256M,the problem is still there.
Everything was perfect before 3/14.

The error message in /var/log/error.log
PHP Notice: unserialize() [function.unserialize]: Error at offset 0 of 17833 bytes in /var/www/drupal5/includes/bootstrap.inc on line 342
PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 86228 bytes) in /var/www/drupal5/includes/database.mysqli.inc on line 167

When I turn off some modules by SQL query, The web page shows "Page not found" and the following message:

* warning: array_keys() [function.array-keys]: The first argument should be an array in /var/www/drupal5/includes/menu.inc on line 1224.
* warning: Wrong parameter count for min() in /var/www/drupal5/includes/menu.inc on line 1224.

Thanks for your help!

eaton’s picture

eaton commented
Title: unserialize() fails in menu.inc » unserialize()ing cached data fails, puppies die
Component: menu system » base system

I see that problem with DRUPAL-5-2dev now as well, I didn't spot that last night. That points to something OTHER than the menu system modifications that I was suspicious about, since they only hit HEAD. A couple people on #drupal suggested http://drupal.org/node/126867 might be the culprit but I'm not sure how the two lines it changed would affect things so dramatically.

bdragon’s picture

bdragon commented

Subscribing

eaton’s picture

eaton commented
Status: Active » Fixed

Fixed by unconed. The db_query patch was in fact causing the problem. Whew!

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)