2:00pm 21st January 2014
I dont know why this fixed it, or what chrome changed that caused the code to break but if anyone is interested in what we did to resolve the error i'll explain.
1) I made all events going out of swfobject and our swf code go directly to the Flash.js class we had to interface with flash. Before it was propagating through a Backbone.dispatcher to the flash class. That caused the aw snap error to go away.
2) We were using a datetime library called Moment.js version 2.2.0. It was the one throwing the maximum call stack error, after updating that to 2.3.0 it stopped. Would love to know what chrome changed to cause a infinite loop.
If anyone has info on what chrome changed between the two versions that caused either error, I would love the answer because its a bit scary fixing the symptoms but not knowing the cause.
12:53am 21st January 2014
chrome will open multi tasks in the task manager, and it is sensitive to many plugins
try the following
1- go to settings in chrome 2- open extentions 3- disable all the extensions that you can 4- close chrome 5- open task manager in windows 6- go to processes 7- close all the processes related to chrome 8- reopen chrome and check your problem again