[Tracking Requested - why for this release]: Steps To Reproduce: 1. Open https://mail.google.com/ and sign-in 2. Open Web Console (Ctrl+Shift+k) 3. Wait to complete loading the page --- observe error message 4. Click an mail --- unable to view the mail body 5. Reload (F5) --- observe error message Actual Results: Error in Web console: CustomError: Error in protected function: Expected int32 as second argument <unknown> unable to view the mail body Expected results: No error Able to view the mail body Regression window: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c69d8db6828a4f39118a64c96a5f1a52b27e9170&tochange=4964d9484814
Summary: CustomError: Error in protected function: Expected int32 as second argument <unknown> → Gmail does not load in 2015-08-15 nightly (CustomError: Error in protected function: Expected int32 as second argument <unknown>)
My $0.02 : reverting commit from bug 830329 fixes this bug.
Oops, I meant bug 890329 :)
I'm investigating and will in all likelihood land a backout in a bit.
url: https://hg.mozilla.org/integration/mozilla-inbound/rev/9b34691fd5cda4be9ad9674a0883f51de2198d69 changeset: 9b34691fd5cda4be9ad9674a0883f51de2198d69 user: Till Schneidereit <firstname.lastname@example.org> date: Sat Aug 15 23:58:24 2015 +0200 description: Bug 1195030 - Backout of bug 890329 for breaking email reading in gmail. r=bustage
The error is still very mysterious to me, but I backed the offending patch out for now and will investigate more offline. People do like to be able to read their mails, after all.
For future reference, you should probably have landed the backout on m-c directly rather than counting on someone to merge inbound on your behalf over the weekend. That way nightly testers don't get hosed in the mean time.
3 years ago
Happening here Windows 10 x64 Error began with build 43.0a1 (2015-08-15) x64 Tried non electrolysis window, new profile, safe mode.
Nightly still has the problem of open Gmail
The actions referenced in comments 7 and 11 did not make into the regular nightly build process which kicks off automatically just after 3 AM each morning. Also, as mentioned in comment 9, the backout should have been done on mozilla-central, not just inbound so that it would have been picked in the overnight build process without needing to be merged in from inbound.
Nightlies containing the backout from comment 11 have shipped (there was a respin on Saturday specifically for this backout and the regularly-scheduled Sunday builds).
Assignee: nobody → till
Status: NEW → RESOLVED
Last Resolved: 3 years ago
status-firefox41: --- → unaffected
status-firefox42: --- → unaffected
status-firefox43: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla43
Tracking for 43 in case it breaks again.
tracking-firefox43: ? → +
In Dev Edition as of 2015-08-18 (which should have the backout?), I'm seeing a very similar error which is preventing me from creating new documents in Google Docs: CustomError: Error in protected function: Operation is not supported <unknown> (4x) and then Google Docs says "Something went wrong; try reloading". Disabling e10s makes no difference. Viewing emails in Gmail, the original problem listed in this bug, _does_ work, but my spider-sense says it may well still be related, given the timing. Gerv
The code that broke gmail was landed on Mozilla Central after merge day so was never on Aurora.
(In reply to Gervase Markham [:gerv] from comment #16) > In Dev Edition as of 2015-08-18 (which should have the backout?), I'm seeing > a very similar error which is preventing me from creating new documents in > Google Docs: > > CustomError: Error in protected function: Operation is not supported > <unknown> > (4x) > > and then Google Docs says "Something went wrong; try reloading". Disabling > e10s makes no difference. Viewing emails in Gmail, the original problem > listed in this bug, _does_ work, but my spider-sense says it may well still > be related, given the timing. > > Gerv I've filed Bug 1195795
You need to log in before you can comment on or make changes to this bug.