[Email] Attaching any file to email will cause Email app to freeze

RESOLVED WORKSFORME

Status

defect
RESOLVED WORKSFORME
5 years ago
4 years ago

People

(Reporter: jlee, Assigned: asuth)

Tracking

({regression})

unspecified
ARM
Gonk (Firefox OS)
Dependency tree / graph

Firefox Tracking Flags

(blocking-b2g:2.2+, b2g-v2.0 unaffected, b2g-v2.1 unaffected, b2g-v2.2 fixed)

Details

(Whiteboard: [2.2-exploratory-2], )

Attachments

(1 attachment)

Reporter

Description

5 years ago
Description:
When composing an email, after any file is attached the Email app will freeze. Must restart Email app to use (minus attachment functionality).
   
Repro Steps:

*Logged in email account in Email app

1) Update a Flame device to BuildID: 20141218040201
2) Open Email app > tap Compose
3) Attach any file to the email (video, picture, audio)
4) After file is attached, observe Email app functionality (attempt to type, send, attach another file, go to Inbox, etc)
  
Actual:
Attaching any file to an email will cause the Email app to freeze. Cannot use Email app until restarting the app.
  
Expected: 
Attaching any file to an email will not cause the Email app to freeze. All supported files can be attached to an email.
  
Environmental Variables:
Device: Flame 2.2 Master (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141218040201
Gaia: 58734e8a48157f99d5b733412b600c2e04c954fe
Gecko: 5c7a6294b82a
Gonk: e5c6b275d77ca95fb0f2051c3d2242e6e0d0e442
Version: 37.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
  
  
Repro frequency: 100%, 4/4
See attached: video clip (http://youtu.be/E_ELdLIoruQ), logcat (emailattach_logcat.txt)
Reporter

Updated

5 years ago
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
Depends on: 1113340
Reporter

Comment 1

5 years ago
Issue does NOT occur on Flame 2.1 or Flame 2.0.

Attaching any file to an email will not cause the Email app to freeze. All supported files can be attached to an email.

Device: Flame 2.1 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141219001200
Gaia: 6af3d029bae3a14f400fec0926f0f8ad7b579b4b
Gecko: d41f6bd64343
Gonk: e5c6b275d77ca95fb0f2051c3d2242e6e0d0e442
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Device: Flame 2.0 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141219000200
Gaia: ce83ea7b8e3fa2d1c3fd771fc22b654c18b3c381
Gecko: f57067657bfa
Gonk: e5c6b275d77ca95fb0f2051c3d2242e6e0d0e442
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Keywords: regression
[Blocking Requested - why for this release]:

Nominating to block 2.2. Users should be able to attach files to an Email without issue. Poor UX, and a regression.
blocking-b2g: --- → 2.2?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
QA Contact: ddixon
A fix has landed on inbound in bug 1113340 with a mochitest to prevent regressions.  It should ideally merge to trunk today and ideally be in tomorrow's build.  At that time we can resolve this chain of bugs fixed.
Mozilla Inbound Regression Window

Last Working

Device: Flame 2.2
BuildID: 20141217065133
Gaia: d22dfece04fc00457e8369c660c11f945b088d2f
Gecko: aa82fdbf3362
Gonk: Could not pull gonk.  Did you shallow Flash?
Version: 37.0a1 (2.2) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

First Broken

Device: Flame 2.2
BuildID: 20141217071133
Gaia: d22dfece04fc00457e8369c660c11f945b088d2f
Gecko: 9d0ed89e7c58
Version: 37.0a1 (2.2) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Last Working Gaia and First Broken Gecko
Issue DOES occur here. 
Gaia: d22dfece04fc00457e8369c660c11f945b088d2f
Gecko: 9d0ed89e7c58

Last Working Gecko and First Broken Gaia
Issue DOES NOT occur here. 
Gaia: d22dfece04fc00457e8369c660c11f945b088d2f
Gecko: aa82fdbf3362

Gecko Pushlog: 
hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=aa82fdbf3362&tochange=9d0ed89e7c58

Possible Cause: 

Bug 701634 - (AsyncIDB) IndexedDB: Support database access from worker threads
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
based on comment 3 a fix is already underway - so not taking any action on the regression window at this time.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Contact: ddixon
blocking-b2g: 2.2? → 2.2+
Depends on: 1120336
This is not reproducible on master. Can we double check if it's still reproducing?
Keywords: qawanted
This should continue to reproduce on master until bug 1120336 has landed, at least for ActiveSync.
Maybe the STR is different or the attached file should be very large?
Yes, different/more specific STR (comment 0 didn't mention a specific account type, although it should have).  Bug 1120336 is a real thing that affects our ActiveSync implementation.  IMAP was only affected by bug 1113340.
Ah, ok. I see there is an eye put on this. Just trying to reduce blockers and then I see this one. If anyone can assign only to remark the bug is watched over. Thank you!
(taking to clarify this bug is owned/being addressed; currently we're just waiting on review and landing on bug 1120336.)
Assignee: nobody → bugmail
Status: NEW → ASSIGNED
QA Contact: ychung
Bug 1120336 has landed, resolving as WFM to convey there's no specific fix needed here, just our dep being present.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
QA Contact: ychung
Removing qawanted keyword as it is resolved as worksforme.
Keywords: qawanted
You need to log in before you can comment on or make changes to this bug.