Unfortunately, no - we aren't able to reproduce this kind of issue in the explorer or desktop examples, and haven't heard reports of one quite like this before (though if it only happened in IE6/7/8 I might have something for you), which makes this sound like it is either something application specific, or something else going wrong in Chrome itself.

Chrome has the interesting characteristic that it creates several processes to manage all of its tabs - there is an internal tool that manages memory details for each process. In the tools menu, select "View Background Pages" to see these details - maybe more light can be shed on the issue there. Don't forget to activate other columns to see what else it has to offer.

Sorry, by debugging-at-a-distance skills only stretch so far. You could consider trying to break out the likely culprit into its own entrypoint, so that it runs on its own, isn't as complex as your whole project, and still causes the issue. If you were able to do this, you could post it here so others could try to solve what might be causing it.