Closed Bug 531668 Opened 15 years ago Closed 14 years ago

New Firefox 3.6b4 Crash [@ _PR_MD_ATOMIC_DECREMENT | nsHttpChannel::Release() ] Search Mozill

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 531663

People

(Reporter: moh.maskuri, Unassigned)

Details

(Keywords: crash, Whiteboard: dupme?)

Crash Data

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; id; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; id; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4

Bugzilla@Mozilla – Bug 531663

Reproducible: Always
Priority: -- → P2
Severity: normal → critical
Keywords: crash
Summary: New Firefox 3.6b4 Crash [ @_PR_MD_ATOMIC_DECREMENT | nsHttpChannel::Release() ] Search Mozill → New Firefox 3.6b4 Crash [@ _PR_MD_ATOMIC_DECREMENT | nsHttpChannel::Release() ] Search Mozill
Why are you filing a new bug for the same crash signature?

Priority should only be set by developers please. resetting to --
See https://bugzilla.mozilla.org/page.cgi?id=fields.html#priority
Priority: P2 → --
Whiteboard: dupme?
Going to go ahead and dupe.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Crash Signature: [@ _PR_MD_ATOMIC_DECREMENT | nsHttpChannel::Release() ]
You need to log in before you can comment on or make changes to this bug.