Closed Bug 49814 Opened 25 years ago Closed 24 years ago

Crashed due to gRDF being null

Categories

(SeaMonkey :: Bookmarks & History, defect, P5)

x86
FreeBSD
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: jesup, Assigned: bugs)

Details

(Keywords: crash, Whiteboard: [nsbeta3-][PDTP5][cut 0919])

Attachments

(1 file)

I was going back (using the Go menu dropdown) from file:///tmp to a list of Query results from bugzilla and crashed. We crashed due to gRDF being null in nsBookmarksService::GetLastCharset. Note that gRDFC is _not_ null; I can't see how this can happen from a simple inspection unless we were in the middle of dropping the refcnt - but we don't appear to be. Fresh pull and build 8/21/00.
Keywords: crash
Nav triage team: nsbeta3+, reassigning to radha; QA team please reproduce.
Whiteboard: [nsbeta3+]
Nav triage team: P1
Priority: P3 → P1
not surprisingly, I can't reproduce this with the 2000082508 build on linux Red Hat 6. That really doesn't mean much though, the original report is on FreeBSD and the steps to repro haven't been solidly linked to the actual crash. I've now added no useful information in response to the request, sorry.
PDT setting priority to P5 unless this can be reproduced on Mac, Windows or Linux x86.
Priority: P1 → P5
Whiteboard: [nsbeta3+] → [nsbeta3+][PDTP5]
Cut for beta 3 and rtm.
Whiteboard: [nsbeta3+][PDTP5] → [nsbeta3-][PDTP5][cut 0919]
Reassigning 79 Bookmarks bugs to Ben. I was told this was going to be done shortly about two months ago, but it clearly hasn't been. I think that's long enough for all these bugs to remain assigned to nobody. Feel free to filter all this spam into the trashcan by looking for this string in the message body: ducksgoquack
Assignee: slamm → ben
Netscape Nav triage team: this is not a Netscape beta stopper.
Keywords: nsbeta1-
Severity: normal → critical
rjesup@wgate.com - are you still hitting this problem? If so, it seems any more info you can give us would be appreciated. Gerv
I have not seen this again, at least not in a long time (I don't think I saw it more than once or twice). It may have been a random crash due to someone trashing memory they didn't own (or didn't own anymore). I don't see this currently.
so i'll mark this WFM and leave it to randell to click verified.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: