Opened 9 years ago

Closed 9 years ago

#9013 closed defect (Invalid)

Running a custom command in mainmenu cannot allocate memory

Reported by: jms@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

I'm trying to run a command 'free' from frontend's mainmenu, this worked fine in 0.23.1. In 0.24 problem occurs after I have watched a livetv channel (no matter what channel). There is no problem if I run command from menu before I start livetv.

Error message (full frontend's log attached):

2010-09-26 19:36:44.311 Launching: /usr/bin/free >/tmp/loki
2010-09-26 19:36:44.314 myth_system('/usr/bin/free >/tmp/loki'): Error: fork() failed because Cannot allocate memory

Attachments (3)

mythfrontend.log (10.1 KB) - added by jms@… 9 years ago.
mainmenu.xml (2.5 KB) - added by jms@… 9 years ago.
mediacentermenu's mainmenu.xml
mem.log (602 bytes) - added by jms@… 9 years ago.
Memory usage before and after livetv launch

Download all attachments as: .zip

Change History (8)

Changed 9 years ago by jms@…

Attachment: mythfrontend.log added

Changed 9 years ago by jms@…

Attachment: mainmenu.xml added

mediacentermenu's mainmenu.xml

Changed 9 years ago by jms@…

Attachment: mem.log added

Memory usage before and after livetv launch

comment:1 Changed 9 years ago by beirdo

Milestone: 0.24unknown

comment:2 Changed 9 years ago by beirdo

If fork is failing with this error, this means the system is telling you you do not have enough memory to do the fork, which creates a complete copy of the current process. Your best bet is to create a swapfile, and activate swap. Running with no swap is not a very wise choice, especially with 1.5G (it seems). MythTV is a memory-hungry application, and the in-memory footprint may well be larger than your available memory.

I suggest also that you read the manpage for fork. At the bottom, it indicates the error returns. If you are running with resource limits, you may need to tweak.

comment:3 Changed 9 years ago by jms@…

Ok, I'll add a swap as a first thing. I have tried to avoid all disk writing until now because this frontend's hardware is quite low-end (dedicated htpc without a hard disk, just a usb key).

comment:4 Changed 9 years ago by jms@…

You are right, after utilizing a swap the problem went away. Thank you.

comment:5 Changed 9 years ago by robertm

Resolution: Invalid
Status: newclosed
Note: See TracTickets for help on using tickets.