Closed GoogleCodeExporter closed 8 years ago
I'm experience this as well. This is so annoying.. I can't read all the console
logs and that turns debugger messages useless.
Please, fix this asap.
Original comment by jobertod...@gmail.com
on 31 Jul 2015 at 5:54
For which version of the Chromecast firmware are you seeing this issue? When do
you last remember it working correctly?
Are you using any extensions or antivirus programs that may be interfering with
the debugger?
Original comment by jonathan...@google.com
on 3 Aug 2015 at 5:07
It never worked for me.. although I just started debugging it fews days ago.
Chromecast firmware: 38401
Extensions:
- Bookmark Manager
- ColorZilla
- GBBD Banco Santander (Brasil) S.A
(https://chrome.google.com/webstore/detail/gbbd-banco-santander-bras/idnljhnpjeg
fbcohjhdnhjlnfnffmbnf?utm_source=chrome-app-launcher-info-dialog)
- Gmelius for Inbox by Gmail
- Google Cast
- Google Inbox Checker (Inbox by Gmail)
- JSON Formatter
- Postman - REST Client
- SearchPreview
- Turn Off the Lights
- Unlimited Free VPN - Hola
However, I even tested on incognito mode (only Turn off The Lights are enabled)
and it doesn't scroll either.
Original comment by jobertod...@gmail.com
on 3 Aug 2015 at 5:31
[deleted comment]
One more thing, I even tried to debug on Chrome Canary, which I just installed,
that is, it is a brand new installation, no extensions whatsoever.
Also, I have another related issue: when I click "console" tab, all other tabs
(networks, source, etc) are hided and a can't go back to them.
Original comment by jobertod...@gmail.com
on 3 Aug 2015 at 6:32
Attachments:
The Chromecast firmware version that I reported the issue with was 38401. I
last remember it working correctly a week and a half ago (Week of July 20th
2015) although I could be mistaken.
Original comment by BlinginB...@gmail.com
on 4 Aug 2015 at 4:24
We're looking into it and will let you know if we need any additional
information.
Original comment by jonathan...@google.com
on 5 Aug 2015 at 12:17
I've been having this issue since last few days, it is extremely unusable. I've
even tried debugging using an incognito window - both on ubuntu (Version
44.0.2403.125 (64-bit)
and OSX Chrome (Version 44.0.2403.127 (64-bit))
Original comment by shail...@aboutobjects.com
on 5 Aug 2015 at 12:18
This issue still exists with Ubuntu Chrome Version 44.0.2403.130 (64-bit)
Original comment by shail...@aboutobjects.com
on 5 Aug 2015 at 10:43
I was told a workaround for this and have verified it works for me. While
you have the chromecast debugger dev tools open, open the Chrome developer
tools (via shortcut keys or from hamburger tools menu). Find the style for
"console-messages" div and add "height:100px". Unfortunately you have to redo
this every time the dev tools tab is switched.
Original comment by shail...@aboutobjects.com
on 5 Aug 2015 at 11:49
I can confirm that I am also seeing this on the latest version of OSX with
Chrome version 44.0.2403.125
Original comment by JeffreyK...@gmail.com
on 13 Aug 2015 at 5:20
I've also just tested on windows 8.1 running Chrome 44.0.2403.155 m with no
extensions, and I'm seeing the same issue.
Original comment by JeffreyK...@gmail.com
on 13 Aug 2015 at 5:25
Issue 633 has been merged into this issue.
Original comment by jonathan...@google.com
on 14 Aug 2015 at 4:00
I am also experiencing this issue.
Original comment by mfrangi...@gmail.com
on 21 Aug 2015 at 2:46
The issue seems to be resolved for me at the moment finally
Original comment by BlinginB...@gmail.com
on 21 Aug 2015 at 2:48
For those who may still be seeing an issue with the debugger, note that you
might have the broken version of devtools cached. If that's the case, you can
try clearing the cache by doing the following:
- Navigate to chrome://appcache-internals
- Find the entry for
https://chrome-devtools-frontend.appspot.com/serve_rev/@196004/196004.manifest
- Click the 'remove' link under that
If you continue to have issues with the debugger after that, please let us know.
Original comment by jonathan...@google.com
on 21 Aug 2015 at 6:18
Closing this ticket as it seems to be resolved. If you experience the error
again in the future, do let us know here.
Original comment by jonathan...@google.com
on 10 Sep 2015 at 4:17
Original issue reported on code.google.com by
BlinginB...@gmail.com
on 31 Jul 2015 at 1:18Attachments: