3

I'm getting an error on line 975 ( this is what the console reports ), but when I look at the code it is clearly not 975.

Cannot read property E of undefined:

Here is a screenshot: enter image description here

Here is the screenshot showing the disparity for ...

enter image description here

  • What is the actual error line? – markthethomas Jul 11 '14 at 21:38
  • the console reports 975, why, I said that already, do you want a screen shot? –  Jul 11 '14 at 21:39
  • 1
    Sorry, maybe I wasn't clear: what do you think the actual error line should be? (trying to get at the disparity between what you think it should be + why and what the console reports) :) – markthethomas Jul 11 '14 at 21:41
  • screenshot added for your disparity –  Jul 11 '14 at 21:48
  • Yes; edited the question to help you clarify. What have you tried to solve the problem? Moving your code a line down...anything? – markthethomas Jul 11 '14 at 21:48
  • 1
    so you want me to validate the failure of Google on my own? and then what? –  Jul 11 '14 at 21:49
  • Not 'validate the failure of google', but rather help you actually solve your problem. If you haven't tried anything to fix it or see why it's reporting that line, we can't be of much help on here. – markthethomas Jul 11 '14 at 21:51
  • 1
    Presumably the error is related to one of the `this.E.xxx` references prior to that, it's the only `E` in the code. So somehow `this` has become undefined. – Barmar Jul 11 '14 at 21:54
  • 1
    Have you used the debugger's `{}` tool to reformat the code? Maybe that confuses the line numbers. – Barmar Jul 11 '14 at 21:55
  • @Barmar - no I have not I do not know what that is. –  Jul 14 '14 at 13:21
  • @user3293653: It's activated by default imho. It will pretty-print your code, and the debugger uses the line numbers of the pretty code not your minified/original one. – Bergi Jul 14 '14 at 14:17
  • @Bergi That's not my experience, but maybe there's a hidden preference that controls it, and one of us has changed it from the default (I went through chrome://flags 6-9 months ago, I don't remember all the things I tweeked). – Barmar Jul 14 '14 at 15:57

1 Answers1

0

It's possible Chrome isn't reporting the specific line, but using line 975 as a reference to the segment of the code where property E doesn't seem to be found, thus line 975 could be in the middle of whatever code is problematic (some debuggers do this instead of reporting the first line they find a problem on - maybe Chrome's interpreter works like this, I don't know though, since I use Firefox for development instead). In that case, it would mean that this is what's undefined and there's your problem.

We'd have to see more to get a grip on why this would be happening since we can't determine what the context for this is from the screenshot. What is the expected value of this and if this is part of an object definition that you instantiate later, how do you instantiate it, as the context could matter for the value of this.

mechalynx
  • 1,306
  • 1
  • 9
  • 24