chrome debugger throwing Uncaught TypeError with google sidebar gadget for Calendar

[Art Wu]

I've been seeing this for the last one or two weeks with the chrome debugger running for any google gadget running in google calendar's container. When this occurs the gadget fails to load. This only occurs when the debugger is on; with debugger on it occurs ~90% of loads. This can be reproduced by loading http://www.google.com/calendar/render?gadgeturl=http://www.google.com/ig/modules/hello.xml with and without the debugger.

[PhistucK]

1. When did this start occurring?

2. Does it ever occur on other browsers?

3. Does it reproduce when launching Chrome with the following command line flag?

--js-flags="--nocrankshaft"

(This flag disables JavaScript optimizations)

☆PhistucK

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.

[Art Wu]

Answers and additional info-

1.  Definitely after 1/30/17 1:30PM EST. More likely within the last two weeks.
2. On Firefox, I began seeing XML Parse Errors (screenshot) over this same timeframe.
   
3. Yes with the below flag, when dev tools are open and upon visiting the second page in this sequence
   
   1. https://www.google.com/calendar/render?gadgeturl=http://www.google.com/ig/modules/hello.xml
   2. https://www.google.com/calendar

It's likely a change in behavior with Google Calendar's gadget container (but I was directed here from the calendar group; please redirect me if there's a more relevant group). The frequency of this occurring seems to vary from ~10% to ~90% of page loads, depending on the day. In Chrome, gadgets fail to load when this error occurs. In Firefox, gadgets still load and function.

☆PhistucK

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[PhistucK]

1. Chrome 56 was released on desktop in 2017-1-25 (it is a gradual release), so it sounds like it started with Chrome 56.

This might be a Chrome change (throwing new exceptions for certain XML parsing errors that break the code, for example).

2. On the other hand, if those Firefox errors (while not having the same consequences Chrome has) also started right about then, it might be a Google Calendar issue...

3. I meant, without the Developer Tools feature being active, with a gadget that used not to reproduce it while the Developer Tools feature was inactive.

For reporting Google Calendar issues, use the "Send feedback" menu option under the cog-wheel menu in Google Calendar (sorry I cannot be more helpful here).

For reporting Chrome issues, you can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.

[Art Wu]

Since I've seen likely related errors in both FF and Chrome, I've reported via Google Calendar's feedback option. Re: question 3, the reference Hello World gadget will load on Chrome without the "We're sorry..." popup with dev tools off and won't load with dev tools on, triggering the popup and the Uncaught TypeError.

☆PhistucK

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[PhistucK]

For what it is worth, I cannot reproduce the issue, with or without the Developer Tools feature, using Chrome 56.0.2924.87 on Windows 7.

Perhaps some extension you have installed is messing things up?

☆PhistucK

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.

[Art Wu]

Interesting. Reproducing it also running Chrome 56.0.2924.87 on Win 7 with all extensions off (but not seeing the error on every load of the calendar page).

☆PhistucK

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[PhistucK]

I refreshed like 10 times, with and without the debugger. Not sure what is going on...

☆PhistucK

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.