Maxthon’s forum admin abc@home, has recently posted an insighful summary of the differences between Google Chrome’s multi-processes feature and Maxthon’s isolator:
Essentially, the anti-freeze technique is to make the user interface (menu, buttons, toolbars etc) independent of the tabs, which contain the browser controls and where problems often arise, and make each tab independent of each other. Chrome uses multi-process to achieve this while Maxthon 2.x uses multi-thread to acheive the same. Yet whether multi-process or multi-thread, it is not possible to be totally independent. There must be inter process/thread communications to be a unity.
Generally processes are more independent than threads. But a thread consumes less resources than a process, and a thread works more efficiently with other threads of the same process than a process working with another processes. Before 2.5.1, the multi-thread technique was limited by the traditional windows framework and did not work as effectively as intended. Maxthon 2.5.1 uses a new windows framework to perfect the implementation.
To read more about the Isolator feature of Maxthon 2.5 visit Maxthon’s official blog.