Castanets
Castanets copied to clipboard
Edge distributed web engine. Part of web engine processes are offloaded to a powerful devices and only graphical results are processed in local devices. This way, we overcome both CPU limitations and...
Sub-task of #111 File scheme resource should be loaded on Browser side device even when NetworkService is enabled in renderer side device.
We need a tool to analyze the performance of Castanets. Castanets performance is strongly related to the byte amount, frequency and transfer rate of data sent and received to sync...
**Describe the bug** DCHECK resource_pool.h(148)] Check failed: !is_gpu_. While enabling debug build , and solving prior DCHECK issues, this DCHECK is hit. BT below [28562:28586:0808/173703.640595:FATAL:resource_pool.h(148)] Check failed: !is_gpu_. #0 0x7f65a0cf3e8d...
Currently we use ashmem for android shared memory by using posix platform handle definition in castanets. By default we create only RW mode shared memory region using ashmem. We didn’t...
Goal : Load resources directly on renderer side device without network transfer. Network service sends Mojo DataPipe to transfer the loaded resources to renderer. The DataPipe has a ring buffer...
Multimedia support for Castanets differs from traditional Chromium. In traditional chromium, renderer process reads multimedia stream and decodes using MM pipeline, which then writes to the frame buffer. In Castanets,...
* Move resource loading to the renderer process The module of resource loading is located and run in browser process. It causes performace degradation because resources are sent to renderer...