Joey Parrish 0a59da4146 Free segment memory after storage ...

Although DownloadManager clears the segment list as soon as it has
started the download Promise chain, the entire list is bound into the
each download function.  This is subtle and difficult to address
directly.

Instead, we set the segment data to null explicitly after the segment
is stored.  In this way, we are sure to only have one segment buffer
in memory at a time during a storage operation.

Note that there is no regression test to go along with this, because
ArrayBuffer memory consumption cannot be directly instrumented from
JavaScript, weak references cannot be used to track which buffers are
garbage collected, and the buffer references are bound into anonymous
functions and therefore cannot be found by exploring object
hierarchies.

Closes #1167

Change-Id: Ifeccbfb2d15a1a0243524c92e36512f9308fd5c6

2017-12-08 12:12:47 -08:00

..

db_engine.js

Moved Legacy Variant Ids Resolution into DBEngine

2017-12-06 00:39:07 +00:00

download_manager.js

Free segment memory after storage

2017-12-08 12:12:47 -08:00

i_storage_engine.js

Add Type Structure to Storage Engine

2017-12-04 22:41:23 +00:00

offline_manifest_parser.js

Add Type Structure to Storage Engine

2017-12-04 22:41:23 +00:00

offline_scheme.js

Add Type Structure to Storage Engine

2017-12-04 22:41:23 +00:00

offline_utils.js

Moved Legacy Variant Ids Resolution into DBEngine

2017-12-06 00:39:07 +00:00

storage_engine_factory.js

Add Type Structure to Storage Engine

2017-12-04 22:41:23 +00:00

storage.js

Use Manifest Duration for Offline Manifest Duration

2017-12-07 21:38:43 +00:00