Closed Bug 1014197 Opened 11 years ago Closed 10 years ago

crash in nsCOMPtr<nsIFTPEventSink>::nsCOMPtr<nsIFTPEventSink>(nsIFTPEventSink*) | mozilla::net::CacheFile::RemoveChunk(mozilla::net::CacheFileChunk*)

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
x86
Windows NT
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1011771

People

(Reporter: mayhemer, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-da7866c2-ef20-477a-8863-2876c2140517. ============================================================= Similar: https://crash-stats.mozilla.com/report/index/af37c529-fcb1-427d-8d35-a64902140520 This one's look pretty bad: Crash Address 0x5a5a5a5e. I remember similar problem we had with with CacheFileHandles, fixed in bug 945945. Maybe similar rewrite is needed?
Very few hits on those, but yes, when we see them, they have the poison address: https://crash-stats.mozilla.com/report/list?signature=nsRefPtr%3CnsSAXAttributes%3E%3A%3AnsRefPtr%3CnsSAXAttributes%3E%28nsSAXAttributes%2A%29+%7C+mozilla%3A%3Anet%3A%3ACacheFile%3A%3ARemoveChunk%28mozilla%3A%3Anet%3A%3ACacheFileChunk%2A%29 https://crash-stats.mozilla.com/report/list?signature=nsCOMPtr%3CnsIFTPEventSink%3E%3A%3AnsCOMPtr%3CnsIFTPEventSink%3E%28nsIFTPEventSink%2A%29+%7C+mozilla%3A%3Anet%3A%3ACacheFile%3A%3ARemoveChunk%28mozilla%3A%3Anet%3A%3ACacheFileChunk%2A%29
Crash Signature: [@ nsCOMPtr<nsIFTPEventSink>::nsCOMPtr<nsIFTPEventSink>(nsIFTPEventSink*) | mozilla::net::CacheFile::RemoveChunk(mozilla::net::CacheFileChunk*)] → [@ nsCOMPtr<nsIFTPEventSink>::nsCOMPtr<nsIFTPEventSink>(nsIFTPEventSink*) | mozilla::net::CacheFile::RemoveChunk(mozilla::net::CacheFileChunk*)] [@ nsRefPtr<nsSAXAttributes>::nsRefPtr<nsSAXAttributes>(nsSAXAttributes*) | mozilla::net::CacheFile::RemoveCh…
I think this one is a dup of bug 1011771 as well.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
No longer blocks: cache2afterenable
You need to log in before you can comment on or make changes to this bug.