Google Chrome's recent stable release causes a "Page(s) unresponsive" alert when users edit NetCommunity pages. The full message reads: "The following page(s) have become unresponsive. You can wait for them to become responsive or kill them." Subsequently, users are unable to save changes from the edit window. The issue appears limited to the edit window popup which is consistent with a known bug involving the Window.open() function. The issues have occurred almost universally since Google pushed the January 17 update (version 32).
Version 33 will resolve the issue, but its stable release won't be available until late-February. In the meantime, users have three options:
(1) Use a differentWeb Browser (Firefox, Safari, or Internet Explorer)