Not especially urgent. Apologies if this should be posted under Devel's issue queue. Running:
PHP 4.3.9
Devel 6.x-1.7
Views Beta 2
Zen 6.x-1.x-dev
(All modules/themes up to date)

Using the Zen theme, a block-type view spews raw data (below). Using the Garland theme, the page loads fine and just doesn't display the block-type view.

Views Block:

  1. Turn on devel module in left sidebar
  2. Enable Theme Developer
  3. (Turn off Themer Info checkbox)
  4. Surf to a page with a Views block enabled in the right sidebar
  5. Page fills with raw output:
    Array ( [default] => views_display Object ( [db_table] => views_display [vid] => 4 [id] => default [display_title] => Defaults [display_plugin] => default [position] => 1 [display_options] => Array ( [style_plugin] => default [style_options] => Array ( ) [row_plugin] => fields [row_options] => Array ( ) [relationships] => Array ( ) [fields] => Array ( [title] => Array ( [id] => title [table] => node_revisions [field] => title [label] => Title [relationship] => none [link_to_node] => 1 ) [teaser] => Array ( [id] => teaser [table] => node_revisions [field] => teaser [label] => Teaser [relationship] => none ) )
    ---SNIP---
    [items_per_page] => 3 [use_pager] => 0 [pager_element] => 0 [offset] => 0 [title] => Building Profiles ) [handler] => *RECURSION* ) ) ) ) )

Views Page (this occurs using both Zen theme and Garland):

  1. As above
  2. Surf to a Views page
  3. White Screen

Comments

merlinofchaos’s picture

When you get a white screen, does a message appear in your apache/php error log?

moshe weitzman’s picture

can you upgrade to php 4 or 5? noone tried devel_themer with 4.3

lrickard’s picture

@merlinofchaos: Memory exceeded.

PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 1703122 bytes) in /var/www/vhosts/example.com/httpdocs/drupaltest/sites/all/modules/devel/devel.module on line 1351

I'm going to look into updating PHP with my provider. I'm happy to answer more questions about this, but as I said, it's not urgent for me. Updating PHP is probably a better use of everyone's time.

lrickard’s picture

Following up: On Media Temple, upgraded to fastCGI PHP 5.1.4. Default upgrade gives 24M memory_limit.

A page view still throws WSOD.
A block view now throws WSOD instead of returning raw data.

In both cases, the Apache error log gives memory exceeded messages:
[Wed Apr 30 09:37:03 2008] [warn] mod_fcgid: stderr: PHP Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 1706698 bytes) in /var/www/vhosts/example.com/httpdocs/drupaltest/sites/all/modules/devel/devel.module on line 1351

After upping memory_limit to 32M:
[Wed Apr 30 09:58:47 2008] [warn] mod_fcgid: stderr: PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 1706698 bytes) in /var/www/vhosts/example.com/httpdocs/drupaltest/sites/all/modules/devel/devel.module on line 1351

In case it wasn't clear above, this ONLY happens with Theme Developer enabled. Everything's fine when it's turned off.

moshe weitzman’s picture

Title: Theme developer breaks views output? » Theme developer requires a lot of memory

Yes, it takes a lot of memory to do what theme developer does. Anyone is welcome to profile it and see where savings can be won.

merlinofchaos’s picture

http://drupal.org/node/241408 is duplicate (and the guy has 128M of memory available, so there's something wrong here).

bixed’s picture

Subscribing

plach’s picture

Same problem. My configuration:

ApacheFriends XAMPP (basic package) version 1.6.5
+ Apache 2.2.6
+ MySQL 5.0.51
+ PHP 5.2.5 (memory_limit = 256M, also tried 512M), mod_php SAPI

Devel 6.x-1.7
Views Beta 2

I get this both with Garland and a custom theme, both with a block view and a page view:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1118968 bytes) in
[...]\sites\all\modules\devel\devel.module on line 1351.

Pedro Lozano’s picture

I think the problem is in the _devel_print_object() function from devel.module

Aparently that functions avoids infinite recursion when the object passed is an array with cyclic references, but it doesn't work when the argument is an object.

You can reproduce it like this:

  $var = new stdClass();

  $var2 = new stdClass();
  $var2->ref = $var;

  $var->ref = $var2;

  $output = _devel_print_object($var);

In this case Theme Developer is trying to call _devel_print_object($view), and members of $view have members that point to the $view itseft, causing the infinite recursion.

ravenous’s picture

Ah bingo. Same issue here.
Disabling Devel Node Access and Theme Developer and Views is happy again.

merlinofchaos’s picture

Project: Views (for Drupal 7) » Devel
Version: 6.x-2.0-beta2 » 6.x-1.x-dev
Component: Miscellaneous » devel_themer
Priority: Minor » Normal

At this point I'm going to guess this is a problem in devel.module -- it may be that it's having trouble with recursion because views objects have backreferences.

moshe weitzman’s picture

Status: Active » Closed (duplicate)

yup, true. this is a dupe of a long issue in devel queue

Steve Dondley’s picture

I can confirm. I bumped up to 256M memory limit and was still having issues. It occurs with the devel_theme module turned on.

digitalfrontiersmedia’s picture

Drupal 6.11
Devel 6.x-1.16

Devel up and running fine.

Install
Views 6.x-2.5

At admin/build/modules:
Activate the Views module
immediate WSOD upon page load

Modify {system} table to deactivate Views and get back into site.
Refresh.

At admin/build/modules:
Turn off Devel.
Turn on Views.
Submit.
Everything A-Okay, but can't run both together.

PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 104759 bytes) in .../includes/menu.inc on line 965

PHP memory set to 250M (local value, Master value = 32M)
Mosso cloud
PHP 5.2.6

Theme Developer was NOT turned on.

Hope this helps.