Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Out of Memory Error when running DLNA
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-11-25
05:17 PM
2012-11-25
05:17 PM
Out of Memory Error when running DLNA
I consistently get an out of memory error when I try to run dlna. In my system log it says :
I have three files in three different drives; about 12,000 total; a mix of music and video. I have the DNLA debug version set up and the log for that shows no real probs (just the usual ignoring of flv files, etc.).
From frontview, here's my setup:
Model: ReadyNAS Ultra 2 Plus [X-RAID2]
Serial: <REMOVED BY MODERATOR>
Firmware: RAIDiator 4.2.22
Memory: 1024 MB [DDR3]
Any ideas on how I can solve this out of memory problem? Anything I can try? Is there a way to "break up" the DNLA search into smaller parts? The files that ARE scanned, before the Out of Memory error, ARE discoverable on my other devices...
Nov 25 15:41:13 Gilligan kernel: Out of memory: Kill process 22526 (minidlna) score 539 or sacrifice child
Nov 25 15:41:13 Gilligan kernel: Killed process 22526 (minidlna) total-vm:882024kB, anon-rss:609380kB, file-rss:0kB
Nov 25 16:42:32 Gilligan kernel: xhci_hcd 0000:02:00.0: WARN: Stalled endpoint
Nov 25 16:42:39 Gilligan kernel: xhci_hcd 0000:02:00.0: WARN: Stalled endpoint
Nov 25 16:46:26 Gilligan kernel: minidlna[27817] trap divide error ip:8066480 sp:ffc7d3a0 error:0 in minidlna[8048000+42000]
I have three files in three different drives; about 12,000 total; a mix of music and video. I have the DNLA debug version set up and the log for that shows no real probs (just the usual ignoring of flv files, etc.).
From frontview, here's my setup:
Model: ReadyNAS Ultra 2 Plus [X-RAID2]
Serial: <REMOVED BY MODERATOR>
Firmware: RAIDiator 4.2.22
Memory: 1024 MB [DDR3]
Any ideas on how I can solve this out of memory problem? Anything I can try? Is there a way to "break up" the DNLA search into smaller parts? The files that ARE scanned, before the Out of Memory error, ARE discoverable on my other devices...
Message 1 of 4
Labels:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-11-25
05:20 PM
2012-11-25
05:20 PM
Re: Out of Memory Error when running DLNA
I should add, in case it's relevant: here's the code from my mem_info.log:
MemTotal: 1011764 kB
MemFree: 604360 kB
Buffers: 7188 kB
Cached: 124596 kB
SwapCached: 125612 kB
Active: 54424 kB
Inactive: 250984 kB
Active(anon): 44808 kB
Inactive(anon): 130408 kB
Active(file): 9616 kB
Inactive(file): 120576 kB
Unevictable: 1524 kB
Mlocked: 4 kB
SwapTotal: 524272 kB
SwapFree: 267452 kB
Dirty: 140 kB
Writeback: 0 kB
AnonPages: 52844 kB
Mapped: 8188 kB
Shmem: 24 kB
Slab: 23628 kB
SReclaimable: 10136 kB
SUnreclaim: 13492 kB
KernelStack: 1136 kB
PageTables: 1948 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 1030152 kB
Committed_AS: 502992 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 2336 kB
VmallocChunk: 34359723840 kB
DirectMap4k: 3648 kB
DirectMap2M: 1034240 kB
Message 2 of 4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-11-25
05:21 PM
2012-11-25
05:21 PM
Re: Out of Memory Error when running DLNA
Try downgrading to 4.2.21 and do a full rescan
Message 3 of 4
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-11-25
06:34 PM
2012-11-25
06:34 PM
Re: Out of Memory Error when running DLNA
That did the trick, thanks! Of course the readynas keeps automatically trying to update to 4.2.22 again; is there anyway to stop that until netgear comes up with a version that doesn't cause the out of memory errors? I there a setting I'm missing to stop auto updates?
Also, quick note to netgear: something's broken in your 4.2.22 update that is causing out of memory errors when running an DLNA scan; see above ^
Also, quick note to netgear: something's broken in your 4.2.22 update that is causing out of memory errors when running an DLNA scan; see above ^
Message 4 of 4