hint.js:96 Uncaught ReferenceError: isUndefined is not defined [duplicate] - javascript

Our angular app sometime does not load on chrome canary (Version 41.0.2237.0 canary (64-bit)) saying
Failed to instantiate module ngHintModules due to: RangeError: Maximum
call stack size exceeded
But it loads fine in firefox, chrome (Version 39.0.2171.71 (64-bit)), safari.
Probably not sure whether there is something to do with angular or not.
Full error
Uncaught Error: [$injector:modulerr] Failed to instantiate module ngHintModules due to:
RangeError: Maximum call stack size exceeded
at Array.forEach (native)
at module.exports (chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2333:21)
at module.exports (chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2384:5)
at chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2387:7
at Array.forEach (native)
at module.exports (chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2385:21)
at chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2387:7
at Array.forEach (native)
at module.exports (chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2385:21)
at chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2387:7
NB: The Error I am showing here is from
Version 41.0.2237.0 canary (64-bit)

I also had this problem which was resolved by disabling Batarang.

This issue is opened on the Batarang Github here: https://github.com/angular/angularjs-batarang/issues/156
You can load the prior version of Batarang from this zip file: https://github.com/angular/angularjs-batarang/archive/v0.4.3.zip
Open More Tools->Extensions in Chrome
Locate AngularJS Batarang and click on the trash can to remove the extension
Download the .zip
Extract the file
Open More Tools->Extensions in Chrome
Check Developer Mode at the top
Click 'Load unpacked extension'
Select the directory where you extracted the zip
If you get an error about the manifest file, then you probably selected one directory level too high. Make sure that you select the bottom level angularjs-batarang-0.4.3 directory
Load up an AngularJS page and use Batarang again with Inspector just like before
This will restore the previous version which while having issues does have some mostly working features like Performance profiling, scope inspector, options, and a help tab which are gone from the latest version. The 0.7.1 version fixes the major breakage of apps, but it only provides the scope tree (no inspector) and the new angular-hint functionality.

You don't need to disable Angular batarang; just do the following:
Open the developer tools and navigate to the hint.js file (the one that is triggering the stack overflow)
Go to line 453 add add a breakpoint
reload the app, and when it hits the breakpoint just comment it out (setupModuleLoader(window)) and click continue
It will still throw an exception, (Uncaught ReferenceError: angular is not defined) but you will be able to run batarang
I know it's not the best solution, but that's the quickest thing I could find without going too deep into the problem
Update:
Checking more to what is happening I noticed that the problem happens when we have define multiple modules and we are adding the same dependencies for all of them.
for example:
angular.module("app", ["moduleB", "moduleC"]);
angular.module("moduleB", ["moduleC"]);
When I define the moduleB without passing the same deps with it's parent module, then there is no stack overflow.
angular.module("moduleB", []);

Our team just experienced this error and it was fixed by updating the Batarang Extension in Chrome to the latest.

Update...
With the new update of Chrome, the problem is back, so if anyone experienced this error, revert back to previous build of Chrome.
All builds available here, don't pick the first one.
http://www.slimjet.com/chrome/google-chrome-old-version.php
Then it should work fine!

I had the same problem with GitHub pages site (with Jekyll).
Searched for hours why does AngularJS app didn't show up (ng-cloak was never resolved).
Figured out that was Batarang which causing the issue.
Great thanks for #kpg's answer.

Related

Did Puppeteer get an update recently? Because it's been breaking a lot

I do some stuff on repl.it and recently I've been getting error involving chrome r594312 and a failed download, and I resolved it by just starting a new repl and copying the code (I often don't care about the reasoning, just if it works at the end).
ERROR: Failed to set up Chromium r818858! Set
"PUPPETEER_SKIP_DOWNLOAD" env variable to skip download.
Something along the lines of this with a couple more errors. Now I thought this was just a me problem until I found out the puppeteer demo was broken too. https://try-puppeteer.appspot.com/ I mean, I fixed the issue temporarily for myself but I'm kinda curious what the reasoning for it is. this is no longer the case, but the error on the demo was
Error running your code. TimeoutError: Timed out after 30000 ms while trying to connect to Chrome! The only Chrome revision guaranteed to work is r594312

Unknown error HERE maps AbstractMarker error in mapjs-core

HERE map error
I've contacted the HERE dev support team and they could not give me an answer as to what would cause this error. I am hoping someone else has run across this error. We have a code base that has not been changed in a month and everything was working fine. Then one day this error started happening and prevents the Map from even loading.
The top error in the image is the one that is reporting from the HERE JS SDK and I believe to be the first domino in my other errors.
Please download new available lite SDK android version 4.x. Please refer the new methods and optional parameters at the following reference :
developer.here.com/documentation/maps/api_reference/H.map.AbstractMarker.html

mixpanel-2-latest.min.js:9 Mixpanel error: "mixpanel" object not initialized

mixpanel-2-latest.min.js:9 Mixpanel error: "mixpanel" object not initialized. Ensure you are using the latest version of the Mixpanel JS Library along with the snippet we provide.
From the last couple of days, I am seeing this error in the console when I do inspect element in my Google Chrome. I am using the latest Chrome version 64. I am not using mixpanel. It's also showing up if I open any public website. Any idea how to resolve this error?
Check your extensions, for me it was 'Page Ruler' (https://chrome.google.com/webstore/detail/page-ruler/jlpkojjdgbllmedoapgfodplfhcbnbpn?hl=nl) that caused this error. Systematically disable all extensions until the error does not occur anymore.
I started getting this error out of the blue. It was the chrome extension PageRuler. I trashed PageRuler and the error went away.
Alternatively, you can go to Page Ruler's options menu, and uncheck "Send Anonymous Usage Statistics".
This will enable you to continue using the extensions without seeing the error message.
That's correct. The Page ruler plugin is the one who cause the console error "Mixpanel error: "mixpanel" object not initialized".
Disable it and all good to go
"Free Video Downloader" is another cause.
Check your extensions, for me, it was 'Page Ruler'.
No need to remove 'Page Ruler', Instead of removing do the following...
Page Ruler's options menu, and uncheck "Send Anonymous Usage Statistics".
I checked all given answere in here. All sayed to disable the "Send Anonymous Usage Statistics" checkbox in the settings....
I think hiding a problem is not solving a problem. Since there were a newer version of PageRuler (i had 2.1.2, newest is currently 2.1.3) I deinstalled the old one, reinstalled the new one and from now on, no matter if I send stats or not, error doesn't appaers anymore.

Uncaught TypeError: this.get(...).querySelectorAll is not a function

I am a pretty big project, it is made with angular , node , express.
When I start my application I get the following error:
Uncaught TypeError . This.get ( ... ) is not a function querySelectorAll
But the application continues running without any problem apparently .
I do not know what could be causing this error because as you can see in the screenshot , the error takes about VW838 files called and other angular.
I do not know when this error appeared.
Can anybody help me? Thanks!
This is the error screenshot:
SOLUTION
I've solved it uninstalling and installing chrome again.
Very likely it's caused by some chrome extension.
You can disable chrome extensions one by one and reload your page to see whether the error exists.
Search for .get(0).querySelectorAll in the Chrome extensions folder and all subfolders. Most likely it's .get(0) based on the direct use of querySelectorAll afterwards.
See this disscussion

GWAN is modifying jquery.min.js to error

I am doing an experimental HTML template wich comes with jquery.min.js file - one of the most popular javascript libraries.
When I load the template from my local hard drive it works fine.
When I upload it and load it from server (GWAN) I get error (I think is not the only one) in Chrome looks like this:
Uncaught SyntaxError: Unexpected token { jquery.min.js:3
I inspected a bit and realized there is a
function $
which was turned into
function$
by GWan. The space removed is causing an error in Chrome, Firefox and Safari. I haven't tested other browsers but my IDE also reports a syntax error in the downloaded from GWAN version of the JS file.
I have also tried uploading the files to another server (Apache) and no problem there. The js file was not modified...
Any clues on how to get over this? I suppose there is a bug in javascript on-the-fly optimization of GWan?
Thanks.
It's a known issue and it will be fixed in next release (soon)
You'll be able to disable minifying directly from a init.c script in G-WAN v4.10+, this way:
u8 *www_mini = (u8*)get_env(argv, USE_MINIFYING);
if(www_mini)
{
*www_mini = 0;
puts("> disable minifying");
}
You just have to wait for few days for the new v5 release.

Categories