Anna Posted August 2, 2017 Share Posted August 2, 2017 Hi, I am getting this error ("invalid x,y parameters-not a number) when I left click on the entities or drag around. This is happening only in google chrome version -59.0.3071.86. If we downgrade or upgrade the version it is working fine! The values which we are passing (typeof is a number). So we cdn't figure out why only for a particular version it is showing this error. We have a team using this application and we cannot ask each and everyone to upgrade or downgrade the version. Could someone please help me out here. Quote Link to comment Share on other sites More sharing options...
Parasyte Posted August 2, 2017 Share Posted August 2, 2017 Hi! Click on the left-most arrow to get a stack trace. You can also enable "pause on uncaught errors" in the debugger, which will allow you to inspect the actual values of x and y, and (may be more important) walk the stack to find where those values originate. Debugging in this manner is best done with the non-minified melonJS build. Give it a try and let us know if you manage to track it down. If you need additional support, please don't hesitate to respond here with further information. Best of luck! Quote Link to comment Share on other sites More sharing options...
Arcanorum Posted August 3, 2017 Share Posted August 3, 2017 How did this end up on the game showcase bar? ecv 1 Quote Link to comment Share on other sites More sharing options...
Anna Posted August 3, 2017 Author Share Posted August 3, 2017 I have no idea. I just uploaded the screenshot in the topic. Quote Link to comment Share on other sites More sharing options...
Hashasm Posted August 3, 2017 Share Posted August 3, 2017 here is the description screen it may help you to understand the error @Parasyte Quote Link to comment Share on other sites More sharing options...
Parasyte Posted August 3, 2017 Share Posted August 3, 2017 @Hashasm Were you able to get the variable state during that stack trace as well? I'm interested in the values of all the variables on lines 20135 and 20136. It seems like NaN is getting introduced in some way. But this is only a guess, based on the error message. Quote Link to comment Share on other sites More sharing options...
Hashasm Posted August 4, 2017 Share Posted August 4, 2017 hi , I checked on that lines lines 20135 and 20136 its giving the proper coordinate value not returning any NAN . i wonder why only for this browser version its giving such error. Note my melon version is : melonJS 4.1.1 Quote Link to comment Share on other sites More sharing options...
Parasyte Posted August 4, 2017 Share Posted August 4, 2017 Are you inspecting those variables in the same stack frame that crashed? What about the variables at the rest of the stack frames? Quote Link to comment Share on other sites More sharing options...
Hashasm Posted August 7, 2017 Share Posted August 7, 2017 yes in the same stack .. Quote Link to comment Share on other sites More sharing options...
obiot Posted August 7, 2017 Share Posted August 7, 2017 On 8/3/2017 at 1:10 PM, Hashasm said: here is the description screen it may help you to understand the error @Parasyte but it does not makes any sense... if the me.Vector2d class is throwing an exception, it means that somewhere along the line, one the above method is passing a non numerical value to the other one. can you test the following example and report if you are having the same issue ? http://melonjs.github.io/melonJS/examples/shapes/ I'm running Chrome Version 59.0.3071.115 (Official Build) (64-bit) Chrome right now, and the above example is working fine here. Are you using any complex CSS/elements in your page that might affect the pointer position as seen/detected by melonJS ? Also, maybe you could look at sending us a strip down version of your code (including the html page), so that we can reproduce the issue and identify what is wrong? Quote Link to comment Share on other sites More sharing options...
Hashasm Posted August 7, 2017 Share Posted August 7, 2017 @obiot It will work for the chrome version which you are using. Only for version 59.0.3071.86 it is not working I checked the link. Its showing the same error in this particular version of chrome. Please check the images. Quote Link to comment Share on other sites More sharing options...
Hashasm Posted August 17, 2017 Share Posted August 17, 2017 hi guys , is anyone find out the solution for the above problem please let me know if you guys find anything on the same Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.