Open
Bug 1854668
Opened 3 years ago
Updated 3 years ago
Using MOZ_CC_LOG causes WorkerShutdownDump failures
Categories
(Core :: Cycle Collector, defect)
Core
Cycle Collector
Tracking
()
NEW
People
(Reporter: saschanaz, Unassigned)
Details
- Set
MOZ_DISABLE_CONTENT_SANDBOX=t - Set
MOZ_CC_LOG_DIRECTORYto some directory - Set
MOZ_CC_LOG_ALL=1 - Set
MOZ_CC_LOG_THREAD="worker" - Run some page in
./mach runand close it
C:\Users\sasch\Documents\GitHub\gecko-dev [bug1854640]> $env:MOZ_DISABLE_CONTENT_SANDBOX="t"
C:\Users\sasch\Documents\GitHub\gecko-dev [bug1854640]> $env:MOZ_CC_LOG_DIRECTORY="$env:USERPROFILE\gc-cc-logs\"
C:\Users\sasch\Documents\GitHub\gecko-dev [bug1854640]> $env:MOZ_CC_LOG_ALL="1"
C:\Users\sasch\Documents\GitHub\gecko-dev [bug1854640]> $env:MOZ_CC_LOG_THREAD="worker"
C:\Users\sasch\Documents\GitHub\gecko-dev [bug1854640]> ./mach run
0:00.38 'C:/Users/sasch/Documents/GitHub/gecko-dev/obj-x86_64-pc-windows-msvc\dist\bin\firefox.exe' -no-remote -wait-for-browser -profile 'C:\Users\sasch\Documents\GitHub\gecko-dev\obj-x86_64-pc-windows-msvc\tmp\profile-default' -attach-console
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error: Can't find profile directory.
console.error: ({})
[Parent 20916: Main Thread]: D/WorkerShutdownDump Found ActiveWorker (dedicated): chrome://global/content/translations/simd-detect-worker.js
[Parent 20916: Main Thread]: D/WorkerShutdownDump Principal: [System Principal]
[Parent 20916: Main Thread]: D/WorkerShutdownDump LoadingPrincipal: [System Principal]
[Parent 20916: Main Thread]: D/WorkerShutdownDump BusyCount: 0
[Parent 20916: Main Thread]: D/WorkerShutdownDump CrashInfo: dispatch failed
[Parent 20916: Main Thread]: D/WorkerShutdownDump Found ActiveWorker (dedicated): resource://activity-stream/lib/PersonalityProvider/PersonalityProviderWorker.mjs
[Parent 20916: Main Thread]: D/WorkerShutdownDump Principal: [System Principal]
[Parent 20916: Main Thread]: D/WorkerShutdownDump LoadingPrincipal: [System Principal]
[Parent 20916: Main Thread]: D/WorkerShutdownDump BusyCount: 2
[Parent 20916: Main Thread]: D/WorkerShutdownDump CrashInfo: IsChromeWorker(resource://activity-stream/lib/PersonalityProvider/PersonalityProviderWorker.mjs)
[Parent 20916: Main Thread]: D/WorkerShutdownDump Found ActiveWorker (dedicated): resource://gre/modules/PageThumbsWorker.js
[Parent 20916: Main Thread]: D/WorkerShutdownDump Principal: [System Principal]
[Parent 20916: Main Thread]: D/WorkerShutdownDump LoadingPrincipal: [System Principal]
[Parent 20916: Main Thread]: D/WorkerShutdownDump BusyCount: 0
[Parent 20916: Main Thread]: D/WorkerShutdownDump CrashInfo: dispatch failed
[Parent 20916: Main Thread]: D/WorkerShutdownDump Found ActiveWorker (dedicated): resource://services-settings/RemoteSettings.worker.mjs
[Parent 20916: Main Thread]: D/WorkerShutdownDump Principal: [System Principal]
[Parent 20916: Main Thread]: D/WorkerShutdownDump LoadingPrincipal: [System Principal]
[Parent 20916: Main Thread]: D/WorkerShutdownDump BusyCount: 0
[Parent 20916: Main Thread]: D/WorkerShutdownDump CrashInfo: dispatch failed
console.error: (new AbortError("IOUtils: Shutting down and refusing additional I/O tasks", (void 0), 885))
JavaScript error: resource://gre/modules/CrashManager.sys.mjs, line 922: AbortError: IOUtils: Shutting down and refusing additional I/O tasks
RunWatchdog: Mainthread nested event loops during hang:
--- (no nested event loop active)
Is this expected? Having crashinfo here sounds like something bad happened.
Updated•3 years ago
|
Severity: -- → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•