Bug #101
closed
[30555] Memory exhaustion rescanning video database
Added by anthonyb about 14 years ago.
Updated over 11 years ago.
Category:
Scraper (Music/Video Metadata
Description
Running Build 30555 and decided to rebuild my MyVideos database.
Started a scan of my movies folder - 784 .avi files all with pre-made .nfo files from media Companion and .tbn and fanart.jpg
Got to about the 770th .avi file and noticed that it just stopped.
Log starts showing things like:
19:27:51 M: 12963840 ERROR: CPicture::CacheImage Unable to create new image special://xbmc/UserData/Thumbnails/Video/Fanart/4b1ad069.tbn from image smb://ANTDATAVAULT/Videos/Movies/Weirdsville (2007)-fanart.jpg
19:28:35 M: 425984 SEVERE: DLL: Q:\system\ImageLib.dll : malloc failed, crash imminent (Out of memory requesting 1555240 bytes)
19:28:36 M: 376832 SEVERE: DLL: Q:\system\ImageLib.dll : malloc failed, crash imminent (Out of memory requesting 6220840 bytes)
and then ultimately stops with
19:39:12 M: 12550144 WARNING: XFILE::CFileFactory::CreateLoader - Unsupported protocol(stack) in stack://smb://ANTDATAVAULT/videos/movies/x-men (2000) cd1.avi , smb://ANTDATAVAULT/Videos/Movies/X-Men (2000) CD2.nfo
19:39:51 M: 28672 ERROR: CPicture::CacheImage Unable to create new image special://xbmc/UserData/Thumbnails/Video/Fanart/5d4c81de.tbn from image smb://ANTDATAVAULT/Videos/Movies/X-Men (2000)-fanart.jpg
19:39:53 M: 13398016 ERROR: [[VideoInfoScanner]]: Exception while scanning.
Full log here - http://pastebin.ca/1925035
Files
what is the resolution of "smb://ANTDATAVAULT/Videos/Movies/Weirdsville (2007)-fanart.jpg" ? are any of your fanarts pics very large (look at the ones before / after this one also)
This is also weird:
WARNING: XFILE::CFileFactory::CreateLoader - Unsupported protocol(stack)
I wonder where the hell that's coming from.
maybe anthonyb can post the XMEN.nfo?s creating those errors Arnova means...
Looking at your log: Isn't you're harddrive just running out of free space?
@exobuzz "are any of your fanarts pics very large"
Guess that depends on the definition of large :)
592 of the 607 fanart pics are under 1MB, the remainder are between 1-2MB with one oddly large one (6MB). Everything either side of, and including, the Weirdsville fanart in under 500K.
@bulkzooi "post the XMEN.nfo?s creating those errors Arnova means"
sure, any data you want to look at just let me know.
@arnova "Isn't you're harddrive just running out of free space"
No, there is 2GB+ free space
Could you try moving the 6Mb fanart file out of the way, rescan and see whether this fixes it?
Could you also test with a newer SVN version and provide a new debug log of it (it should at least fix the stack warnings)?
Could you check r30586 (or better)? It contains some workarounds that may remedy this issue.
Will do. I just grabbed 30588 so will try with that one.
OK, just tried rescanning my movies with 30588 and exact same result, in fact, it was displaying the same movie (X-MEN) as when it bombed out previously. New logs attached.
Oh... forgot to mention that the 6MB fan art image is gone too.
I'm wondering whether it's a permission problem on your Windows server. Furthermore I'd suggest testing whether older version experience the same issue...
Permission problem in what way though? Does it need to have write access to the folder it is scanning on the Windows server, and if so, why?
There's no read access issues as it does successfully scan in the poster and fan art and after the scanning bombs out, I reboot the Xbox, start off the 'scan for new content' and it merrily picks up right where it left off and completes my collection.
Am happy to test an older version. Any suggestions on how far back I should go, based on changes you are aware of the the video scanning components?
Well nothing specific I can think of but I would start with checking whether 9.04-1 (stable) from t3ch has the problem too and work from that...
I remember having an issue similar to this a while back, and it was a permission problem. Some files worked fine but other ones caused a lock-up and failed scraping/playing of content.
The way I fixed it which is probably worth a try, just set whatever folder your movies are in to not be shared, then set it to being shared again. Sometimes, after new files are added, Windows sharing does not set the permissions correctly, but doing this will make sure they are all good.
- Target version changed from 3.0 to Future / Pending
- Resolution set to invalid
- Affected Version set to Future / Pending
closing due to lack of feedback.
- Status changed from New to Closed
Also available in: Atom
PDF