900364 - [zffos1.1][SMS]Crash when view audio attachment at compose UI.

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::SMS, defect)

Description

[RuiLi]

User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.116 Safari/537.36

Steps to reproduce:

1. Launch message app and compose a new message.
2. Select an audio file by clicking attachment icon from Music entry.
3. When an audio file attached successfully and return compose UI.
4. Click the audio file thumbnail and select 'View' option. 


Actual results:

The crash report dialog shows.


Expected results:

The view operation shall be ok.

Comment 1

[Scoobidiver (away)]

Which device and b2g18 changeset?
Please provide the crash ID (see https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Getting_crashes_off_the_Device).

Comment 2

[Lukas Blakk [:lsblakk] use ?needinfo]

Can we try on leo device?  Seems like this reporter was on ZTE device.

Comment 3

[Natalya Kot [:nkot]]

Have tested on Leo:
 -(.3gp) - audio file sent successfully (file size 49.6 KB)
 -(.mp3) - notification "The file you have selected is too large" (the audio file I was attempting to send was 4.11 MB)

Build ID: 20130801070210
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/aff662053ee8
Gaia: ddb922ed002e88d01f71199da32ff75911b455b2
Platform Version: 18.1

The same behavior is observed on Buri:
Build ID: 20130802071207
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/ba71c64705e5
Gaia: 361cfb69e22c0db18e85422bb407550426138009
Platform Version: 18.1
RIL Version: 01.01.00.019.180

Comment 4

[RuiLi]

We tested it on ZTE OPEN device. Here is the log info when crashed:
08-05 09:15:14.231: I/Gecko(1102): IPDL protocol error: could not look up PBlob
08-05 09:15:14.231: I/Gecko(1102): IPDL protocol error: Error deserializing 'remoteBlobChild' (PBlob) member of 'RemoteInputStreamParams'
08-05 09:15:14.231: I/Gecko(1102): [Child 1102] ###!!! ABORT: IPDL error [PBlobStreamChild]: "Error deserializing 'remoteBlobChild' (PBlob) member of 'RemoteInputStreamParams'". abort()ing as a result.: file /home/zte/shared/mozilla_1.1_20130726/out/target/product/roamer2/obj/objdir-gecko/ipc/ipdl/PBlobStreamChild.cpp, line 366
08-05 09:15:14.241: E/Gecko(1102): mozalloc_abort: [Child 1102] ###!!! ABORT: IPDL error [PBlobStreamChild]: "Error deserializing 'remoteBlobChild' (PBlob) member of 'RemoteInputStreamParams'". abort()ing as a result.: file /home/zte/shared/mozilla_1.1_20130726/out/target/product/roamer2/obj/objdir-gecko/ipc/ipdl/PBlobStreamChild.cpp, line 366
08-05 09:15:14.661: I/Gecko(112): ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv

Comment 5

[bhavana bajaj [:bajaj]]

RuiLI,

Can you please help with more details on file size and type ?

Comment 6

[bhavana bajaj [:bajaj]]

QA, can we please run the steps in comment #3 for a ZTE Open to see what happens ?

Comment 7

[RuiLi]

Any type audio file cannot be viewed. I test .amr, .mp3. The size is about 17KB/18KB. In our device build, once click 'View' option on audio attachment, 'Music just crash' message displays. Do you have ZTE OPEN device and ZTE build version? I think you can reproduce this bug very easily.

Comment 8

[Jason Smith [:jsmith]]

(In reply to bhavana bajaj [:bajaj] from comment #6)
> QA, can we please run the steps in comment #3 for a ZTE Open to see what
> happens ?

Not possible. Trying to flash a ZTE partner build results in the device failing to boot.

Comment 9

[Preeti Raghunath(:Preeti)]

Please provide a crash report, change set and crash id, file in question that caused the crash. It will help QA.

Comment 10

[RuiLi]

I run 'adb shell ls -l /data/b2g/mozilla/Crash/Reports/submitted/'. 'No such file or directory' shows.

Comment 11

[Jason Smith [:jsmith]]

(In reply to RuiLi from comment #10)
> I run 'adb shell ls -l /data/b2g/mozilla/Crash/Reports/submitted/'. 'No such
> file or directory' shows.

That isn't the right command. You have a / with no space between Crash and Reports. See below for the right command.

adb shell ls -l /data/b2g/mozilla/Crash\ Reports/submitted/

Comment 12

[RuiLi]

Still 'No such file or directory' even after 'adb shell ls -l /data/b2g/mozilla/Crash\ Reports/submitted/'.

Comment 13

[Jason Smith [:jsmith]]

(In reply to RuiLi from comment #12)
> Still 'No such file or directory' even after 'adb shell ls -l
> /data/b2g/mozilla/Crash\ Reports/submitted/'.

How about:

adb shell ls -l /data/b2g/mozilla/Crash\ Reports/

That will at least tell us that the Crash Reports directory is present.

Comment 14

[RuiLi]

C:\Documents and Settings\zhangruili>adb shell ls -l /data/b2g/mozilla/Crash\ Re
ports/
-rw------- root     root           10 2013-08-07 09:19 InstallTime20130805192636
drwxr-xr-x root     root              2013-08-07 10:03 pending

Comment 15

[Kai-Chih Hu [:khu]]

[Triaged] Agreed that this crash issue should be a blocker.

Comment 16

[Jason Smith [:jsmith]]

(In reply to RuiLi from comment #14)
> C:\Documents and Settings\zhangruili>adb shell ls -l
> /data/b2g/mozilla/Crash\ Re
> ports/
> -rw------- root     root           10 2013-08-07 09:19
> InstallTime20130805192636
> drwxr-xr-x root     root              2013-08-07 10:03 pending

Okay. That means we know the Crash Reports directory is present. So let's try this now:

1. Reproduce the crash over wifi
2. Wait about a minute
3. Run the command in comment 13 - you should see a submitted directory present
4. Now run the command in comment 11 after confirming a submitted directory is present
5. After confirming there's something present in the submitted directory, adb pull that file
6. Attach the resulting file to this bug

Comment 17

[Jason Smith [:jsmith]]

Also - Can you provide the audio attachment that caused the crash? That would help us be able to reproduce this crash in house.

Comment 18

[:gerard-majax]

It works nice on Inari too, with http://archive.org/download/testmp3testfile/mpthreetest.mp3

Comment 19

[RuiLi]

C:\Documents and Settings\zhangruili>adb shell ls -l /data/b2g/mozilla/Crash\ Re
ports/
-rw------- root     root           10 2013-08-08 14:26 InstallTime20130808222758
drwxr-x--- root     root              2013-08-08 15:02 pending
drwx------ root     root              2013-08-08 15:02 submitted

C:\Documents and Settings\zhangruili>adb shell ls -l /data/b2g/mozilla/Crash\ Re
ports/submitted/
-rw-r----- root     root           49 2013-08-08 15:02 bp-8e1bbdea-51f3-4dfe-8b7
7-7412a2130808.txt
-rw-r----- root     root           49 2013-08-08 15:02 bp-97bfc38a-16b1-4b2c-be8
f-f4ece2130808.txt

Comment 20

[RuiLi]

Attachment: test audio file

Comment 21

[Scoobidiver (away)]

Here are crash reports (without debug symbols):
bp-8e1bbdea-51f3-4dfe-8b77-7412a2130808
bp-97bfc38a-16b1-4b2c-be8f-f4ece2130808
They confirm the abort message of comment 4.

Comment 22

[:gerard-majax]

I've tested the proposed AMR file and on a gecko 9747e29cfb029ac39f600bdba09cc74b991dd50d (I'm in the middle of a git bisect for bug 901705) it does not crash on Inari.

Comment 23

[:gerard-majax]

It also does not crash with Gecko 715f6c9cebc6a1a1c03b849ead198287ac7e2c23

Comment 24

[RuiLi]

Can you read our device build info? I'm pullzed by such issue also. In our device and build, this crash is reproduced each time. What can I do for this next? How do I check the version of Gecko?

Comment 25

[Jason Smith [:jsmith]]

Can someone try testing on a ZTE Open 1.1 partner build? This might be a POVB issue potentially.

Comment 26

[Jason Smith [:jsmith]]

(In reply to Jason Smith [:jsmith] from comment #25)
> Can someone try testing on a ZTE Open 1.1 partner build? This might be a
> POVB issue potentially.

Bruce - Can someone on your team address the QA Wanted request here? US QA is currently running into trouble getting the ZTE 1.1 partner builds working, but to my understanding, Walter has ZTE 1.1 partner builds working on your side.

Comment 27

[William Hsu [:whsu]]

I cannot reproduce this bug with following build on Ikura device.
- P752D04_LATAM_FFOS_v1.1.0B03.zip
- Build ID: 20130810074647

Comment 28

[Jason Smith [:jsmith]]

Renom. Three people have tried reproducing this crash on our side, but cannot reproduce across a partner ZTE Open build & Leo build.

RuiLi - What is the build ID of the build you used to reproduce this crash? On our side, we can't reproduce this. Can you try reproducing this on the latest build available?

Comment 29

[RuiLi]

I tested it using our updated version. No crash any more. So maybe the previous version we used is too old. I think the bug should be closed. Thank you all.

Comment 30

[Jason Smith [:jsmith]]

(In reply to RuiLi from comment #29)
> I tested it using our updated version. No crash any more. So maybe the
> previous version we used is too old. I think the bug should be closed. Thank
> you all.

Sounds good. Closing as such.

Comment 31

[Walter Chen[:ypwalter][:wachen]]

I can't reproduce it, too.
By new B03 build from partner.