Open AgFlore opened 6 months ago
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
i believe the issue and the solution still validates.
Describe the bug Due to the patch introduced in #787 , regardless of the
enable-crash-reporter
argv, the crash-reporter is always disabled.--crash-reporter-directory
present.configureCrashReporter
if there is noproduct.appCenter
. There always isn't, is it?Expected behavior
enable-crash-reporter
argv is supposed to be the rightful controller over whetherconfigureCrashReporter
should be run. (check https://github.com/microsoft/vscode/blob/8a19756adf1b689e4f490a871d5067e6c54e3d01/src/main.js#L83C54-L83C75 )enable-crash-reporter
, the directory set for crashDumps (%appdata/VSCodium/Crashpad
by default) should be initilized, containing an emptysettings.dat
and two directoriesattachments
andreports
. Minidumps are to be placed in thereports
dir lest a crash happens someday.My Proposals
submitURL
be empty or undefined,uploadToServer
would be false, making it acceptable tocrashReporter.start()
. So we might as well remove thecrash-reporter.patch
.--crash-reporter-directory <absolute-path>
cli option somewhere in the codium repository (based on infomation from vscode), so that users can have a better understanding of the crash telemetry, and quickly get to how to get dumps when electron crashes.telemetry.enableCrashReporter
has been obselete (and potentially misleading!) since the one-time transition in v1.49, and should be updated.Please confirm that this problem is VSCodium-specific
Please confirm that the issue/resolution isn't already documented