Closed Bug 805856 Opened 12 years ago Closed 11 years ago

Shutdown CC logging doesn't work any more

Categories

(Core :: XPCOM, defect)

All
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox18 --- affected
firefox19 --- affected

People

(Reporter: mccr8, Assigned: mccr8)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 2 obsolete files)

Maybe I am just doing something silly, but bug 800486 seems to have broken cycle collector logging. It seems like this line is failing: NS_GetSpecialDirectory(NS_OS_TEMP_DIR, getter_AddRefs(logFile)); I seem to be returning here: NS_ENSURE_TRUE(logFile, nullptr);
Hmm, so non-shutdown logging seems to be okay, it is just putting it in an annoying directory: /Users/amccreight/Library/Caches/TemporaryItems/cc-edges.49948-1.log
That's basically an NSPR bug. Maybe on shutdown we can't even do NS_GetSpecialDirectory.
> That's basically an NSPR bug. (The stupid directory on macos, that is.)
Yeah, if it is just on shutdown, it isn't a big deal. I can work around it. I was mostly worried about getting user reports. Though that directory is lame. ;)
Summary: default CC logging doesn't work any more → Shutdown CC logging doesn't work any more
Blocks: 723783
This really needs to be fixed, as it is a pain.
Assignee: nobody → continuation
Attached patch hacky workaround, not for landing (obsolete) (deleted) — Splinter Review
Attachment #691875 - Attachment is obsolete: true
Attachment #693971 - Attachment is obsolete: true
Here's a new twist on this problem... shutdown CC logging now trips shutdown write poisoning...
Filed bug 837197 for the write poisoning issue.
Bill says MOZ_CC_LOG_DIRECTORY works, so that's probably a better option than my patch here.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: