Closing a window opened with crashes the phone



6 years ago
5 years ago


(Reporter: amac, Unassigned)



Firefox Tracking Flags

(Not tracked)


(Whiteboard: [b2g-crash])



6 years ago
STR (happens with the build from Mozilla-Central, changeset:   131666:2e6cfac714f6

Although I'm going to use the contacts app on the STR because it's an standard one, I've reproduced it with a simple app that had a simple a w =

1. Open the contacts app.
2. Go to the import Contacts from Gmail or Outlook options.
3. Wait till the logging page finishes loading.
4. Close window with the X at the top left corner

What should happen: 
The window closes and we return to the previous screen

What really happens:
The window closes, the previous screen shows briefly and the B2G parent process crashes.

The only thing I get on the logcat is: 
F/libc    ( 1171): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)

If I close the app instead of closing the window (with the window open, long press the home button and use the task switcher to close the app), then the process doesn't crash.


6 years ago
Severity: major → critical
Keywords: crash
Whiteboard: [b2g-crash]
Can you check to see if there's a crash report ?

If you have adb installed, you can also use this script to see if there's a crash report:

Comment 2

6 years ago
Sorry for the delay in answering. There's no crashreport on the device (and it still crashes with today's build):

Submitted crash reports
/data/b2g/mozilla/Crash Reports/submitted: No such file or directory
Pending crash reports
/data/b2g/mozilla/Crash Reports/pending: No such file or directory

When I press the X to close the window, the first thing that appears on the logcat is:

D/memalloc(  692): /dev/pmem: Allocated buffer base:0x49a00000 size:81920 offset:3526656 fd:126
D/memalloc(  692): /dev/pmem: Allocated buffer base:0x49a00000 size:81920 offset:3608576 fd:142
F/libc    (  692): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
I/DEBUG   (  690): debuggerd committing suicide to free the zombie!
I/DEBUG   (  875): debuggerd: May 21 2013 16:42:27

That's on an engineering build.

Comment 3

5 years ago
I've just tried this again today and it seems that somehow this has been fixed already. Now it's working correctly.

I'm closing this as WFM... cause now it does.
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.