Closed (fixed)
Project:
Media: YouTube
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
11 Dec 2010 at 02:22 UTC
Updated:
3 Jan 2014 at 02:41 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
wojtha commentedComment #2
tolstoydotcomI can confirm this, and I've attached the print_r output for a node I created using one of my own videos. A spot check of some of the items in the 'raw' array shows things that have nothing to do with my video: I've never heard of those users, my video has nothing to do with computers or XMen, etc. etc. I've never seen anything like that coming from Youtube's gdata XML when searching for other videos, but I haven't looked into where all that data is coming from.
Comment #3
Diamonds0a commentedI just encountered a problem that is related. I fixed the issue without getting rid of the data->raw fields but I would like to point out why this is alarming.
In ./modules/node.module line 704 you can see that node_load() will leave nodes in memory that have been loaded.
In my use case, using drupal search which resulted in all youtube videos caused memory usage to go over 128 MB.
Comment #4
aaron commentedThis is now fixed. The update will clear the metadata from your tables, and they will be refilled with the bare minimum for functionality. Developers requiring all the metadata can check that box in API in the module's settings. (For now, that should be done prior to running the update, as the module doesn't currently handle that very well if checking/unchecking the box on the fly.) Also note that in the vast majority of cases, you probably don't need to store the raw data.
Thanks!