1132393 - [FFOS2.0][Woodduck][crash report]MS suddenly crashed when manipulate files

Status: RESOLVED DUPLICATE of bug 1146283

(Firefox OS Graveyard :: General, defect, P2)

Description

[sync-1]

MS suddenly crashed when manipulate files.
     this problem is difficult reproduce.
     the crash reportID is:bp-9648ce19-a97c-4679-8c37-b55832150212
     please slightly check it.
 
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[Josh Cheng [:josh]]

Hi Danny,
Could you please help to check the problem? Thanks!

Comment 2

[Danny Liang [:dliang]]

Hi reporter,
Did you upload symbols on server? (https://developer.mozilla.org/en-US/docs/Uploading_symbols_to_Mozillas_symbol_server)
It's hard to analyze crash issue with only crash report id, because there is no your symbols on server so that we cannot get readable crash report and correct information.
We might need your help to provide readable crash report by following steps:
1. build symbols:
#. setup.sh && make buildsymbols (symbols will put into "objdir-gecko/dist/crashreporter-symbols/“)
2. get dmpfile (xxx.dmp) and extra file will save under “/data/b2g/mozilla/” when segmentation fault
3. Using minidump_stackwalk to parse dmpfile and then get readable crash report.
#./minidump_stackwalk dumpfile objdir-gecko/dist/crashreporter-symbols/ > dmp_result.txt
where minidump_stackwalk is located in http://hg.mozilla.org/build/tools/file/tip/breakpad/

Let me know if any further question. Thanks.

Comment 3

[sync-1]

(In reply to comment #2)
 > Comment from Mozilla:Hi reporter,
 > Did you upload symbols on server?
 > (https://developer.mozilla.org/en-US/docs/Uploading_symbols_to_Mozillas_symbol_server)
 > It's hard to analyze crash issue with only crash report id, because there is no
 > your symbols on server so that we cannot get readable crash report and correct
 > information.
 > We might need your help to provide readable crash report by following steps:
 > 1. build symbols:
 > #. setup.sh && make buildsymbols (symbols will put into
 > "objdir-gecko/dist/crashreporter-symbols/“)
 > 2. get dmpfile (xxx.dmp) and extra file will save under
 > “/data/b2g/mozilla/” when segmentation fault
 > 3. Using minidump_stackwalk to parse dmpfile and then get readable crash
 > report.
 > #./minidump_stackwalk dumpfile objdir-gecko/dist/crashreporter-symbols/ >
 > dmp_result.txt
 > where minidump_stackwalk is located in
 > http://hg.mozilla.org/build/tools/file/tip/breakpad/
 > Let me know if any further question. Thanks.
 
 dear mozilla,
 
      we have upload the build symbol and i can check the Crashing Thread information with the ID.The crash position in the soure tab is:/home/local/build/fire2-35-release/v7G1M-3/gecko/xpcom/build/IOInterposerPrivate.h:48,is there anything wrong with our buildsymbol?

Comment 4

[Danny Liang [:dliang]]

(In reply to sync-1 from comment #3)
> (In reply to comment #2)
>  > Comment from Mozilla:Hi reporter,
>  > Did you upload symbols on server?
>  >
> (https://developer.mozilla.org/en-US/docs/
> Uploading_symbols_to_Mozillas_symbol_server)
>  > It's hard to analyze crash issue with only crash report id, because there
> is no
>  > your symbols on server so that we cannot get readable crash report and
> correct
>  > information.
>  > We might need your help to provide readable crash report by following
> steps:
>  > 1. build symbols:
>  > #. setup.sh && make buildsymbols (symbols will put into
>  > "objdir-gecko/dist/crashreporter-symbols/“)
>  > 2. get dmpfile (xxx.dmp) and extra file will save under
>  > “/data/b2g/mozilla/” when segmentation fault
>  > 3. Using minidump_stackwalk to parse dmpfile and then get readable crash
>  > report.
>  > #./minidump_stackwalk dumpfile objdir-gecko/dist/crashreporter-symbols/ >
>  > dmp_result.txt
>  > where minidump_stackwalk is located in
>  > http://hg.mozilla.org/build/tools/file/tip/breakpad/
>  > Let me know if any further question. Thanks.
>  
>  dear mozilla,
>  
>       we have upload the build symbol and i can check the Crashing Thread
> information with the ID.The crash position in the soure tab
> is:/home/local/build/fire2-35-release/v7G1M-3/gecko/xpcom/build/
> IOInterposerPrivate.h:48,is there anything wrong with our buildsymbol?

Thanks for feedback! We just confused if anything wrong on symbol server.
This crash might relate to media decoder, will update if any finding.
Keep NI for analysis.

Comment 5

[Danny Liang [:dliang]]

By call stack(https://crash-stats.mozilla.com/report/index/9648ce19-a97c-4679-8c37-b55832150212), it crashed at:

#0 mozilla-b2g32_v2_0:xpcom/build/IOInterposerPrivate.h: mozilla::IOInterposer::Monitor::Lock()
#1 objdir-gecko/content/media/../../dist/include/mozilla/Monitor.h: mozilla::MediaTaskQueue::Dispatch(mozilla::TemporaryRef<nsIRunnable>)", "function_offset": "0x11", "line": 92, "module": "libxul.so"
#2 mozilla-b2g32_v2_0:content/media/MediaDecoderStateMachine.cpp: mozilla::MediaDecoderStateMachine::NotifyWaitingForResourcesStatusChanged()", "function_offset": "0x37", "line": 1363, "module": "libxul.so"

Hi Vincent, would you mind take a look on this?

Comment 6

[Vincent Liu[:vliu]]

(In reply to sync-1 from comment #0)
> MS suddenly crashed when manipulate files.
>      this problem is difficult reproduce.
>      the crash reportID is:bp-9648ce19-a97c-4679-8c37-b55832150212
>      please slightly check it.
>  
>  
>   For FT PR, Please list reference mobile's behavior:

Could you please offer a way to reproduce it more easily? Also ni? Blake to analysis, too.

Comment 7

[Blake Wu [:bwu][:blakewu]]

(In reply to sync-1 from comment #0)
> MS suddenly crashed when manipulate files.
How did you manipulate files? 
By knowing how you did, We could add more corresponding logs to find out the rootcause.

Comment 8

[sync-1]

(In reply to comment #6)
 > Comment from Mozilla:(In reply to sync-1 from comment #0)
 > > MS suddenly crashed when manipulate files.
 > How did you manipulate files? 
 > By knowing how you did, We could add more corresponding logs to find out the
 > rootcause.
 
 open an filemanager of our own, it just crashed without any special operation,only occur once as i known.

Comment 9

[Blake Wu [:bwu][:blakewu]]

(In reply to sync-1 from comment #8)
> (In reply to comment #6)
>  > Comment from Mozilla:(In reply to sync-1 from comment #0)
>  > > MS suddenly crashed when manipulate files.
>  > How did you manipulate files? 
>  > By knowing how you did, We could add more corresponding logs to find out
> the
>  > rootcause.
>  
>  open an filemanager of our own, it just crashed without any special
> operation,only occur once as i known.
What does your file manager do? Will it generate thumbnails of video, like video app? 
From the call stack, it seems this file manager was trying to decode video file. That's why I ask.

Comment 10

[sync-1]

(In reply to comment #8)
 > Comment from Mozilla:(In reply to sync-1 from comment #8)
 > > (In reply to comment #6)
 > >  > Comment from Mozilla:(In reply to sync-1 from comment #0)
 > >  > > MS suddenly crashed when manipulate files.
 > >  > How did you manipulate files? 
 > >  > By knowing how you did, We could add more corresponding logs to find out
 > > the
 > >  > rootcause.
 > >  
 > >  open an filemanager of our own, it just crashed without any special
 > > operation,only occur once as i known.
 > What does your file manager do? Will it generate thumbnails of video, like
 > video app? 
 > From the call stack, it seems this file manager was trying to decode video
 > file. That's why I ask.
 
 yes,it will generate thumbnails of video like video app.

Comment 11

[Vincent Liu[:vliu]]

Clear ni? since Blake is working on this.

Comment 12

[[e-mail]]

hi Blake,

   CrashReportID:bp-18360e18-d33e-42f5-862e-370162150305
   i got the same crash when i play RTSP video streaming through browser.
   i have upload the log in 1117486 in comment 183.

Comment 13

[[e-mail]]

Attachment: mtklog.rar

Comment 14

[[e-mail]]

Attachment: 2015-03-05-11-19-22.png

Comment 15

[[e-mail]]

Attachment: 2015-03-05-11-18-44.png

Comment 16

[[e-mail]]

hi Blake,

    we found a way can 100% reproduce this crash.

    REPRODUCING PROCEDURES:
    1.enter Video app,select a video(any video small enough to share through message) to play.
    2.click upper-right button, select share through Messages.
    3.in Message interface, click the video and select "view",meanwhile get a phone to call MS,no matter MS deny or answer the call. 
    4.in Message interface, click the video and select "view" again, can't play video.
    5.wait until MS frozen, unlock MS, it shows crash report window.

Comment 17

[[e-mail]]

Attachment: ttt.3gp a small video for test

Comment 18

[Danny Liang [:dliang]]

NI Blake for comment 16.

Comment 19

[Blake Wu [:bwu][:blakewu]]

Hi Munro, 
Could you help check it?
Thanks!

Comment 20

[Munro Mengjue Chiang [:mchiang] Be Mozillian since 1/19/2018]

I can reproduce the issue with my woodduck device.
From the log, there are lots of fence error in both device & kernel logs.

device:
03-25 02:27:20.337   159   669 E         : GetPrevFBAcquireFd: FB acquire fence is invalid!

kernel:
<6>[  421.302526] (0)[669:Compositor][DISP/SYNC] L3 fence ovl_fence-3-2833(138)
<6>[  421.304266] (0)[77:disp_clean_up_k][DISP/SYNC] L3 signal idx=2833,cnt=1

Comment 21

[Munro Mengjue Chiang [:mchiang] Be Mozillian since 1/19/2018]

Attachment: device.log

Comment 22

[Munro Mengjue Chiang [:mchiang] Be Mozillian since 1/19/2018]

Attachment: kernel.log