Created attachment 8573415 [details] logcat_20150305_1120.txt Description: Gmail is having difficulty signing in, loading messages, etc. Incredibly laggy, non-ending loading loops, failure to synch emails. At one point I was able to get a partial list of my inbox emails but could not interact with them or load the rest of them. This seems to be affecting all branches Repro Steps: 1) Update a Flame to 20150305010212 2) Launch Email app 3) Attempt to log into Gmail Actual: Gmail is not able to log-in, or load messages Expected: No issues logging into Gmail Environmental Variables: Device: Flame Master Build ID: 20150305010212 Gaia: eff3321ab4e65da3f906688ebb55ddf1e93d9452 Gecko: 56492f7244a9 Gonk: e7c90613521145db090dd24147afd5ceb5703190 Version: 39.0a1 (Master) Firmware Version: v188-1 User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0 Repro frequency: 11/12 See attached: logcat
Also seeing this on 2.2 and 2.1 devices Device: Flame 2.2 (KK - Nightly - Full Flash - 319mem) Build ID: 20150305002528 Gaia: 89af288bad6751248ff84504fa898206fee127fe Gecko: 6d8d294aa8f3 Gonk: e7c90613521145db090dd24147afd5ceb5703190 Version: 37.0 (Master) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Device: Flame 2.1 (KK - Nightly - Full Flash - 319mem) Build ID: 20150302001220 Gaia: 5d3479fdd438412adee4452720856b6b771fe5cd Gecko: 9bf4c663241f Gonk: e7c90613521145db090dd24147afd5ceb5703190 Version: 34.0 (2.1) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
PBylenga and I talked about this a bit on IRC. The first log is showing a network timeout which suggests network troubles, and since this appears to be localized to a geographic region, this could also be some type of limited gmail data-center flakeiness for IMAP (as opposed to the web UI backend or the mechanisms used by the iOS and android and other apps that aren't using IMAP). Given the other recent problem we saw with the server saying "NO" to stuff on gmail, this wouldn't be entirely surprising. We left it that some more logs would be gathered (retrieved while reproducing to avoid the short-log-due-to-circular-buffer-overflow issue) and perhaps a tcpdump capture or too. Note that the second log appears to be for yahoo IMAP rather than gmail and doesn't seem to have any obvious problems.
Issue no longer reproduces -
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.