Mythweb Fatal Error memory size exhausted

Bug #141528 reported by Scott
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mythplugins (Ubuntu)
Confirmed
Wishlist
Unassigned

Bug Description

Binary package hint: mythtv

Feisty with latest version of Mythtv (0.20.2)

Mythweb generates the following error when getting a directory listing:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 71 bytes) in /usr/share/mythtv/mythweb/includes/programs.php on line 420

It also froze the live tv for a few seconds.

This was the first time I used MythWeb since we moved to Schedules Direct, previously it worked fine.

On the third attempt it worked but froze my live TV for a few seconds.

On subsequent attempts it worked perfectly.

Revision history for this message
Mario Limonciello (superm1) wrote :

Hi thanks for the bug report. This is sounding more like a configuration related issue. Apache & php may just need to have sizes changed to cope with how much guide data you have. As for live tv freezing a few seconds, this tends to happen on underpowered machines performing a large amount of SQL queries at one time. Can you change PHP memory settings and report back? Thanks.

Changed in mythtv:
importance: Undecided → Wishlist
status: New → Incomplete
Revision history for this message
Eric Logan (erlogan) wrote :

It is notable that this occurs with the default configuration that results from installing the package mythweb.

At least, it did for me.

Revision history for this message
James Purser (purserj) wrote :

This is a config error.

You need to allocate more memory to php, edit the php.ini file and change the following setting:

memory_limit

Set this to something like 20 or 32MB and you should be fine.

Revision history for this message
Mario Limonciello (superm1) wrote :

Since this is a configuration issue, i'm going to close up this bug.

Changed in mythplugins:
status: Incomplete → Won't Fix
Revision history for this message
tallac (b-launchpad-bcarver-endjunk-com) wrote :

Are you sure this is a configuration issue? My memory_limit is set to 128M. I tried increasing it to 256M, and I get the same error. Seems like that should be plenty...

Revision history for this message
Mainiac (mainiac) wrote :

Edit file:

/etc/mythtv/mythweb-htaccess

Line 94:
        php_value memory_limit 32M

change to:
        php_value memory_limit 64M

Revision history for this message
Mario Limonciello (superm1) wrote :

I do see this and it really is here that the bug exists:

/etc/apache2/sites-available/mythweb.conf

Changed in mythplugins:
status: Won't Fix → Confirmed
Revision history for this message
Mark Warriner (warriner) wrote :

The php_value memory_limit setting can be found in three mythweb-related locations:
   1. /etc/apache2/sites-available/mythweb.conf (also symlink from sites-enabled)
   2. /etc/mythtv/mythweb-config.php
   3. /usr/share/mythtv/mythweb/mythweb.conf.apache (also via /var/www/mythweb/...)

From my testing, only #2 seems to have any effect on my hardy system (I changed it from 32M to 128M). Having three places for the same setting makes it very difficult to debug and maintain, especially given the conflicting advice given in these comments and the forums.

Revision history for this message
Geoffrey Pursell (geoffp) wrote :

I found that /etc/apache2/sites-available/mythweb.conf is where my change worked (in Intrepid). I had to restart Apache for it to take effect.

64M seems to work fine for me.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.