Closed Bug 961402 Opened 11 years ago Closed 11 years ago

Application does not always crash when main thread is crashed on gonk

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: sotaro, Unassigned)

Details

During developing Bug 946720, I faced following symptom. - Even after application's main thread is crashed by null pointer access, the applicaiton's process does not abort and continue processing. This finally trigger just a following log. It could hide the actual bug and make hard to debug. > [Parent 134] WARNING: pipe error (153): Connection reset by peer: file /home/sotaro/b2g_master_hamachi/B2G/gecko/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 446 If the application's main thread crashes, the crash log should be printed to logcat and the application process should also crash.
blocking-b2g: --- → 1.4?
OS: Windows 7 → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Some other bugs like Bug 946000 also output the following to logcat. They might be caused by same reason as in Bug 946720 Comment 37. I/Gecko ( 136): [Parent 136] WARNING: pipe error (76): Connection reset by peer: file ../../../gecko/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 446
bent, this is a bug related to "pipe error" caused by application main thread's null pointer access.
See See Bug 946720 Comment 37.
This sounds like either a kernel bug or just a case where the log is being flushed after the process crashes maybe?
bent/sotaro, does the description hold true for all releases or did something land in 1.4 causing this failure (hence nominated to block ) ?
Flags: needinfo?(sotaro.ikeda.g)
Flags: needinfo?(bent.mozilla)
Sorry, I really have no idea what this bug could be.
Flags: needinfo?(bent.mozilla)
The code we're working on is new to 1.4, so you can't really compare to what we had before. However, I would not think that it was something we did - more that it's something that's either a bug, or a misunderstanding on how we should use it in the kernel or other non-Gecko code. This isn't necessarily actionable, but I would like partners to work with us to understand what's going on.
Clear 1.4? Do not need to nominate to block.
blocking-b2g: 1.4? → ---
Flags: needinfo?(sotaro.ikeda.g)
There is not explicit STR. Set to WONTFIX.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.