Javascript error > Is that my fault?[SOLVED]

Hey there,

I've run into this message, on chrome, internet explorer, with version r257.2 :

"Source : localhost:50000

Javascript error!

Uncaught ReferenceError: a is not defined

http://localhost:50000/preview.js , line 4610 (col9)"

NW.js just freezes, like when you have a neverending loop.

Does that mean I've done something, that isn't supposed to be done, that I can fix myself, or is it a legitimate bug? It seems to happen when objects with the platform behavior land on tilemaps and/or Tiledbackgrounds, but I haven't been able to reproduce it on a new project, so there's more to it...? But I had no such issue before r257 and its .2 update, although I think I remember the error message being different before the latter.

Generally JavaScript errors are bugs and should be filed in the Bugs forum following all the guidelines. In this case I think you've run in to an already reported issue with that beta release.

Did you find where that come from?

I got the same issue.

Did you find where that come from?

I got the same issue.

Have you download the latest beta r257.3 and tested it?

Thanks for the message that works now with the r257.3!!