K 10
svn:author
V 6
scottl
K 8
svn:date
V 27
2015-04-29T17:18:41.087717Z
K 7
svn:log
V 326
Revert r282227.  It is clearly incorrect as it frees an object that is still
referenced.  I think that there does exist an unlikely edge case for a
memory leak, but only if a driver is incorrectly written and specifies no
valid range of targets to scan.  That can be fixed in a follow-up commit.

Obtained from:	Netflix, Inc.

END