On other types of projects, you will need to investigate how to change your @import statements to <link> elements.
A bug was reported in Chromium, and apparently a fix was committed back in July. What that means in terms of when it will show up in mainstream Chrome, I’m not sure. I tried Canary last night (9/24/13) and still got the same crash.
Why the heck does Drupal use so many @import statements for CSS??
Any Drupal project means that a whole bunch of CSS files are included in any site. Various pieces of Drupal core, contributed modules, and then there is the theme css that a front end person is actually working on. It’s quite easy to have 40 or more stylesheets included in any project.
Unfortunately, this does not play well with older versions of IE – 8 and below have a limit to how many stylesheets they can cope with using <link> elements. That limit is 31. After that, other stylesheets are not parsed.
To work around that, Drupal uses a series of @import statments instead, so that a site will display correctly in old IE.
This is all intended to happen during development of a site. When it comes time to go to production, Drupal has a CSS aggregation option, which combines all the CSS in the site. A production Drupal site, if properly configured, won’t have dozens of HTTP requests just for CSS!