In 3.1, a typical high-end development workstation can now analyze this binary with relative ease across all the platforms we support.īelow is the maximum memory usage after initial analysis of Chrome (all memory usage data was generated on Linux): In previous versions of Binary Ninja, this would be nearly impossible to analyze on any normal development workstation and would likely require server-class hardware to analyze. This binary is a gigantic 1.37GB in size. Our test binary is a build of Linux Chrome with full symbols.
Memory usage has been significantly improved in 3.1, especially with large binaries containing symbols. Of course, there’s a lot of ways you can measure performance and we’ve improved most of them in this release! Let’s break down the improvements into the following categories:
The headlining feature of 3.1 (and the name of the release) is “Performance”. While many Windows improvements are indeed coming in 3.1, others are now planned for 3.2, the new “Windows” release.
If you were expecting 3.1 to be the “Windows” update, we were too as that was the original plan! However, given the scope of major new features, we split the original release plan into two halves. Are you ready for the next stable Binary Ninja release? 3.1 is live today and contains many major improvements:
