Crash in nsPipe on apprunner startup

VERIFIED WORKSFORME

Status

()

Core
Networking
P2
critical
VERIFIED WORKSFORME
19 years ago
18 years ago

People

(Reporter: Ramiro Estrugo, Assigned: Warren Harris)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Description

19 years ago
Created attachment 1697 [details]
stack trace
(Reporter)

Updated

19 years ago
Severity: normal → critical
Priority: P3 → P2

Comment 1

19 years ago
I attatched a stack trace.  The problem happens 1 in 10 runs of the apprunner.
It might be a race condition.
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
Target Milestone: M12
(Assignee)

Comment 2

19 years ago
Is this still happening? Can you tell what the other threads are doing when you
crash?
(Assignee)

Updated

19 years ago
Assignee: warren → ftang
Status: ASSIGNED → NEW
(Assignee)

Comment 3

19 years ago
When I look at this, it looks like a refcounting problem in nsURLProperties or
nsUNIXCharset. Assigning to Frank to look at/verify.

Updated

19 years ago
Assignee: ftang → warren

Comment 4

19 years ago
From the stack trace, it is a ref count problem of nsPipe::mObserver. The
nsURLProperties code do not have any code which call nsPipe::SetObserver. It
looks like a ref count problem inside nsPipe2.cpp . reassign this back to
warren.
(Assignee)

Comment 5

19 years ago
Is this still happening?

Comment 6

19 years ago
I havent seen it anymore.
(Assignee)

Updated

19 years ago
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → WORKSFORME

Comment 7

19 years ago
Bulk move of all Necko (to be deleted component) bugs to new Networking

component.

Updated

18 years ago
Status: RESOLVED → VERIFIED

Comment 8

18 years ago
Works for me.  Verified Linux 2000010308.
You need to log in before you can comment on or make changes to this bug.