Fix leaks related to the usage of JSE runtime data

Fix leaks related to the usage of JSE runtime data

Per isolate runtime data should be deleted when the associated
isolate's destructed.

Also, the internal of per isolate runtime data is obscure to the JS
engine. So XFA or this class itself has to be in charge of the memory
management. Use smart pointer for it so that the resource
could be released properly.

BUG=pdfium:242
Committed: https://pdfium.googlesource.com/pdfium/+/54be7be992f1cde40b9d5c0e55a119c6cc4e4e02

[Wei Li, 2016-09-21 00:51:58]

The CQ bit was checked by weili@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-09-21 00:52:08]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-21 01:05:04]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-21 01:05:05]

Dry run: This issue passed the CQ dry run.

[Wei Li, 2016-09-21 04:15:32]

Description was changed from

==========
Fix leaks related to the usage of JSE runtime data

Per isolate runtime data should be deleted when the associated
isolate's destructed.

Also, the internals of per isolate runtime data is obscure to the JS
engine. So XFA or this class itself has to be in charge of the memory
management. Use smart pointer for it so that the resource
could be released properly.

BUG=pdfium:242
==========

to

==========
Fix leaks related to the usage of JSE runtime data

Per isolate runtime data should be deleted when the associated
isolate's destructed.

Also, the internal of per isolate runtime data is obscure to the JS
engine. So XFA or this class itself has to be in charge of the memory
management. Use smart pointer for it so that the resource
could be released properly.

BUG=pdfium:242
==========

[Wei Li, 2016-09-21 17:16:11]

weili@chromium.org changed reviewers:
+ dsinclair@chromium.org, tsepez@chromium.org

[Wei Li, 2016-09-21 17:16:12]

pls review, thanks

[dsinclair, 2016-09-21 17:19:33]

The CQ bit was checked by dsinclair@chromium.org

[dsinclair, 2016-09-21 17:19:34]

lgtm

[commit-bot: I haz the power, 2016-09-21 17:19:35]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-21 17:19:51]

Description was changed from

==========
Fix leaks related to the usage of JSE runtime data

Per isolate runtime data should be deleted when the associated
isolate's destructed.

Also, the internal of per isolate runtime data is obscure to the JS
engine. So XFA or this class itself has to be in charge of the memory
management. Use smart pointer for it so that the resource
could be released properly.

BUG=pdfium:242
==========

to

==========
Fix leaks related to the usage of JSE runtime data

Per isolate runtime data should be deleted when the associated
isolate's destructed.

Also, the internal of per isolate runtime data is obscure to the JS
engine. So XFA or this class itself has to be in charge of the memory
management. Use smart pointer for it so that the resource
could be released properly.

BUG=pdfium:242

Committed:
https://pdfium.googlesource.com/pdfium/+/54be7be992f1cde40b9d5c0e55a119c6cc4e...
==========

[commit-bot: I haz the power, 2016-09-21 17:19:52]

Committed patchset #1 (id:1) as
https://pdfium.googlesource.com/pdfium/+/54be7be992f1cde40b9d5c0e55a119c6cc4e...