@TimStone It does. That's a sick closure minification trick :)

(function () { return 1, 2; })() // returns 2

Not that until right now I had any idea that this worked

The unminified structure (keeping minified variable names) looks like this:

if (!a.events)
    return;
$.each(...);
return b;

@balpha Yeah, that was the bit I got confused on at first

But it still returns undefined if !a.events, which the calling code seems to never anticipate happening.

yep, absolutely true

looking at that

fwiw, if that happens, something is broken

a.events should always be there (even if an empty array)

if it's not, it means the initial ajax call failed

which isn't easy to recover from

Since it only happens that first time, my guess is that Chrome is doing something stupid, but it's hard to debug since it's too late to set a breakpoint (and refreshing always fixes the issue).

I know a few people have had a similar issue, although at the end of the day it doesn't seem to happen often enough to worry about too seriously.

It happened to Josh and Rebecca a couple of times. Which means if I want to live, "don't worry about it" is not an option ;)

Hahah ;) Mrozek too, apparently, although he seems to have gotten a different (possibly unrelated) error.