I got the dreadful WSOD while uninstalling Flag Bookmark in my new test site. Before that I hadn't really done anything, and no content was created whatsoever.

Anyway, I tried my best to reproduce it afterwards but was unsuccessful, even after deleting the database & starting fresh with the same basic configuration and retracing what I thought were the original few steps.

I noticed in the error log that I got the following five error messages every time I tried to access any page while WSOD was in effect:

Notice: Undefined index: normal in flag_flag->get_link_type() (line 1202 of /home/mysite/public_html/sites/all/modules/flag/includes/flag/flag_flag.inc).
Warning: array_merge(): Argument #2 is not an array in flag_flag->options() (line 203 of /home/mysite/public_html/sites/all/modules/flag/includes/flag/flag_flag.inc).
Warning: Invalid argument supplied for foreach() in flag_flag->construct() (line 222 of /home/mysite/public_html/sites/all/modules/flag/includes/flag/flag_flag.inc).
Notice: Undefined index: normal in flag_flag->get_link_type() (line 1202 of /home/mysite/public_html/sites/all/modules/flag/includes/flag/flag_flag.inc).
Warning: array_merge(): Argument #2 is not an array in flag_flag->options() (line 203 of /home/mysite/public_html/sites/all/modules/flag/includes/flag/flag_flag.inc).

Another thing that I noticed was that the following infamous error message that I kept getting ever since the beginning of the installation disappeared after I took care of WSOD (even after starting fresh):

Unable to allocate memory for pool.

P.S. I only had the following modules installed & enabled: Admin Menu, Ctools, Flag, Flag Lists, Module Filter, Pathauto, Token & Views

Comments

joachim’s picture

Version: 7.x-3.5 » 7.x-3.x-dev
Category: Bug report » Support request
Status: Active » Fixed

> Notice: Undefined index: normal in flag_flag->get_link_type() (line 1202 of /home/mysite/public_html/sites/all/modules/flag/includes/flag/flag_flag.inc).

That can only have happened if the flag link types weren't found. Together with the 'Unable to allocate memory for pool.' error, it suggests that your APC wasn't able to load the right files due to insufficient memory.

Status: Fixed » Closed (fixed)

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