electron/lib/common
Thiago de Arruda 6ff111a141 perf: don't use JSON to send the result of ipcRenderer.sendSync. (#8953)
* Don't use JSON to send the result of `ipcRenderer.sendSync`.

- Change the return type of AtomViewHostMsg_Message_Sync from `base::string16`
  to `base::ListValue`
- Adjust lib/browser/api/web-contents.js and /lib/renderer/api/ipc-renderer.js
  to wrap/unwrap return values to/from array, instead of
  serializing/deserializing JSON.

This change can greatly improve `ipcRenderer.sendSync` calls where the return
value contains Buffer instances, because those are converted to Array before
being serialized to JSON(which has no efficient way of representing byte
arrays).

A simple benchmark where remote.require('fs') was used to read a 16mb file got
at least 5x faster, not to mention it used a lot less memory.  This difference
tends increases with larger buffers.

* Don't base64 encode Buffers

* Don't allocate V8ValueConverter on the heap

* Replace hidden global.sandbox with NodeBindings::IsInitialized()

* Refactoring: check NodeBindings::IsInitialized() in V8ValueConverter

* Refactor problematic test to make it more reliable

* Add tests for NaN and Infinity
2018-06-13 17:38:31 +10:00
..
api Merge pull request #13050 from electron/3.0.0-deprecations 2018-05-30 09:25:36 +02:00
asar.js 🔧 Disable standard/no-callback-literal where necessary 2017-11-23 13:53:03 -08:00
asar_init.js asar: remove patch to support graceful-fs (#12562) 2018-04-07 10:13:32 -05:00
atom-binding-setup.js Expose builtin v8 modules to AtomSandboxedRendererClient 2017-03-09 20:39:14 -03:00
buffer-utils.js perf: don't use JSON to send the result of ipcRenderer.sendSync. (#8953) 2018-06-13 17:38:31 +10:00
init.js Expose builtin v8 modules to AtomSandboxedRendererClient 2017-03-09 20:39:14 -03:00
parse-features-string.js Coerce features to string 2016-12-02 13:40:31 -08:00
reset-search-paths.js Reuse root path variable 2016-06-23 15:56:29 -07:00