The issue was supposed to have been fixed as of the 2014.1 update released in October.
Please tell us the version & build of DW that you are working on? [Help > About Dreamweaver]
I'm suspecting that Bootstrap is not the problem here, since it works fine on Win machines with way lower configurations than yours.
Are you saving the files on the local HDD or on a shared/remote network drive? Are you including any other external scripts etc along with the Bootstrap files?
Maybe you can just pass me one of the test files at firstname.lastname@example.org & I'll take a look at it.
Just tested this in DW CS6, and I experience no problems until I activate the Live view - saving changes causes everything to slow down to a crawl, and it takes up to a minute for DW to catch up. It is unworkable.
Without live view it works, though, and does not crash.
NetBeans IDE has no issues either - interestingly enough, with the NetBeans connection active, any change I save in Dreamweaver is picked up automatically and faster by NetBeans and Chrome (within a second) than by Dreamweaver itself (without the need to switch to those two)!
1. We're using CC 2014.1, but this occurs in earlier versions of Dreamweaver using the latest Bootstrap 3 apps.
2. Files are on a LOCAL SSD drive.
3. We do not use Live View and it is not activated.
We replicated this issue on 3 machines and 1 laptop. It is not Dreamweaver CC specific, a network issue or a Live View issue.
If we rem out the call to the largest BootStrap CSS file, all our app pages open fine.
Thus, it is clearly connected to BootStrap AND Dreamweaver. Our memory tests indicated that Dreamweaver maxes out of memory, hangs, then crashes.
We also tried minified and non-minified files.
Let me know if you are OK to join us for a remote session, so that we can take a look at the issue.
Drop me an email & I'll share the details with you.