Unhandled exception when logging in to VMWare ESXi 6.x
Reported by
jayjayj...@gmail.com,
Jan 5 2017
|
||||
Issue descriptionChrome Version : Chromium 57.0.2973.0 (Developer Build) (32-bit) Revision d3ba7664a7ebc6e74861602eb9696c7ca0a4ed2e-refs/heads/master@{#441592} OS Windows JavaScript V8 5.7.397 Flash (Disabled) User Agent Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2973.0 Safari/537.36 Command Line "C:\Tools\Chrome\chrome.exe" --profile-directory=Default --flag-switches-begin --flag-switches-end Executable Path C:\Tools\Chrome\chrome.exe Profile Path C:\Users\jasper.gohs\AppData\Local\Chromium\User Data\Default Variations 68ebfce2-34df6b5c 16e0dd70-3f4a17df 90757ebb-3f4a17df b3888d8d-afba0f91 74785582-3f4a17df 241fff6c-ca7d8d80 1e528f0f-15305a2 2a33b90e-3f4a17df cdd7eadf-f5ae51c9 ba3f87da-45bda656 5ca89f9-3f4a17df f3499283-2c7b8482 775ebbd7-3f4a17df 76b48ab8-a2567007 9e201a2b-3f4a17df 9d315c2-ca7d8d80 5274eb09-3f4a17df 8ca44045-3f4a17df 9773d3bd-3f4a17df 93731dca-3f4a17df 2e109477-e2e291f1 1d3ad72e-3f4a17df 64cbdfc2-3f4a17df 6b121ae7-3f4a17df 5139837c-3f4a17df 7f8176d9-3f4a17df f79cb77b-3d47f4f4 b7786474-d93a0620 23a898eb-e0e2610f 7382e39a-3f4a17df 868bda90-3f4a17df 4ea303a6-3f4a17df ce152c12-3f4a17df 3a007b7-3f4a17df 3d7e3f6a-2eb01455 9736de91-3f4a17df 64224f74-fbb2b036 dbffab5d-f51b51 64005e71-fb487281 f069f10b-3f4a17df c5073fab-3f4a17df 867c4c68-3f4a17df 7fc902e8-3f4a17df d747916f-d747916f 477f6800-72c07fe0 6844d8aa-669a04e0 fe05be5f-4ad60575 828a5926-d8f52f32 Compiler MSVC 2015 URLs (if applicable) : internal VMWare ESXi 6.x server Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: NOT TESTED Firefox: OK IE: OK What steps will reproduce the problem? (1) Start chromium 57.0.2972.0 or 57.0.2973.0 (2) go to URL of VMWare ESXi Server (3) Login (4) directly after logging, the unhandled exception is shown What is the expected result? It should work without showing this exception, because it is working with Internet Explorer 11 and Firefox 50.1.0 without any problems. What happens instead? I receive the following unhandled exception: Cause: Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest Version: 1.8.0 Build: 4516221 ESXi: 6.5.0 Browser: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2973.0 Safari/537.36 Exception stack: Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest at https://x.x.x.x/ui/scripts/main.js:263:20611 at l (https://x.x.x.x/ui/scripts/main.js:265:12567) at k.$apply (https://x.x.x.x/ui/scripts/main.js:265:16690) at HTMLInputElement.<anonymous> (https://x.x.x.x/ui/scripts/main.js:267:828) at HTMLInputElement.dispatch (https://x.x.x.x/ui/scripts/main.js:262:14464) at HTMLInputElement.r.handle (https://x.x.x.x/ui/scripts/main.js:262:11251) at prop (https://x.x.x.x/ui/scripts/main.js:263:3018) at n.access (https://x.x.x.x/ui/scripts/main.js:262:6702) at n.fn.init.prop (https://x.x.x.x/ui/scripts/main.js:263:2642) at V.$set (https://x.x.x.x/ui/scripts/main.js:264:21408) This exception is not shown when using Internet Explorer 11 or Firefox 50.1.0. Please provide any additional information below. Attach a screenshot if possible.
,
Jan 6 2017
Could you please confirm if this is resolved from your end and can be closed.
,
Jan 6 2017
No, still occuring in: Chromium 57.0.2974.0 (Developer Build) (32-bit) Revision 8fb8af180ee4c2a3bdd6705aa91022ce0c18dc1c-refs/heads/master@{#441886} OS Windows JavaScript V8 5.7.398 Unfortunately, the ESXi server does not provide any additional logs that could the worth posting here. Or at least I did not find any...
,
Jan 6 2017
,
Jan 9 2017
Sorry, but what does "TE-NeedsTriageFromMTV"? Couldn“t find any explanation or help. By the way: error still pops-up in version: Chromium 57.0.2977.0 (Developer Build) (32-bit) Revision 9c06cb4534c62659b48895b0dde92af653d32d88-refs/heads/master@{#442195} OS Windows
,
Jan 11 2017
I was not able to reproduce the error with: Chromium 57.0.2978.0 (Developer Build) (32-bit) Revision 5347b46f28ff183a55d8858b5a604aeee45d984c-refs/heads/master@{#442520} OS Windows JavaScript V8 5.7.423 The error is back in: Chromium 57.0.2979.0 (Developer Build) (32-bit) Revision 8405306dc23f96549b8e55544d88cbd9ab864f24-refs/heads/master@{#442811} OS Windows JavaScript V8 5.7.434
,
Jan 16 2017
Seems to be fixed again in: Chromium 57.0.2984.0 (Developer Build) (32-bit) Revision 8a637421ef6b1bbfe05708f814a914e57c17a8b6-refs/heads/master@{#443847} OS Windows JavaScript V8 5.7.458
,
Jan 16 2017
Ok, I have to revert my last comment. The error also occured in that version. Just updated to: Chromium 57.0.2984.0 (Developer Build) (32-bit) Revision 7a750184c6b3b009f219dc6a13ba83294eee7612-refs/heads/master@{#443863} OS Windows JavaScript V8 5.7.461 With this version, the error occurs after each and every login. With the version used in comment 7 I could at least login after some tries.
,
Feb 12 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by jayjayj...@gmail.com
, Jan 5 2017