We’re back to 32-bit today, but yesterday’s Mac canary (33.0.1702.2) was quietly released as 64-bit to help shake out any problems with the 64-bit Mac build, as we move closer to releasing it more widely.
So far, we’ve noticed two problems:
- http://crbug.com/316401 — Native Client doesn’t work, although it seems to work properly in an unofficial build at the same revision.
- In crash reports, symbols for system libraries are missing (we just need to upload them) and while most walked stacks are fine, a small number seem implausible.
Another known limitation is that the 64-bit browser will not load 32-bit plug-ins. We’re evaluating whether it needs to. On the other hand, the 64-bit browser is able to load 64-bit plug-ins that the 32-bit browser could not, such as the Java 7 plug-in.
If you have any additional feedback about yesterday’s canary, please let me know. After evaluating all of the feedback, I plan to release 64-bit builds to the canary channel somewhat more regularly.
If you’re interested in using the 64-bit build in your own development, set the target_arch and host_arch GYP variables both to “x64” and run “gclient runhooks”. You can do this by setting the GYP_DEFINES environment variable to "target_arch=x64 host_arch=x64".