[Bug]: Dump files cannot be generated on mac

[cuijindong]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.

Electron Version

28.1.0

What operating system are you using?

macOS

Operating System Version

12.0.1

What arch are you using?

arm64 (including Apple Silicon)

Last Known Working Electron version

No response

Expected Behavior

code

crashReporter.start({
  companyName: "demo",
  uploadToServer: false,
  compress: true,
});
setTimeout(() => {
  process.crash()
}, 3000);

Dump files can be generated in the local development environment

It should also be possible to generate a dump file after the application is built.

Actual Behavior

But after building unable to generate dump file 😭.

Testcase Gist URL

No response

Additional Information

After the application was packaged, I tested it on multiple Macs and found that the dump can be generated normally under the 10.13.6 system version; but not on 12.0.1 or higher versions. Why is this?

[VerteDinde]

🤔 Could you try adding the following snippet to your main process code, before app.whenReady? It's similar to the code you linked above, but pair down the variables to submitURL and uploadToServer, and log the crashDumps path. Make sure this code goes before app.whenReady:

const { app, crashReporter } = require('electron')

console.log(app.getPath('crashDumps'))
crashReporter.start({ submitURL: '', uploadToServer: false })

Then reproduce the crash. Let me know if that is still not working.

[electron-issue-triage]

Hello @cuijindong. Thanks for reporting this and helping to make Electron better!

Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.

Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.

Now adding the blocked/need-repro Needs a test case to reproduce the bug label for this reason. After you make a test case, please link to it in a followup comment. This issue will be closed in 10 days if the above is not addressed.

[cuijindong]

🤔 Could you try adding the following snippet to your main process code, before app.whenReady? It's similar to the code you linked above, but pair down the variables to submitURL and uploadToServer, and log the crashDumps path. Make sure this code goes before app.whenReady:

const { app, crashReporter } = require('electron')

console.log(app.getPath('crashDumps'))
crashReporter.start({ submitURL: '', uploadToServer: false })

Then reproduce the crash. Let me know if that is still not working.

I always call crashReporter before app.whenReady. The problem is that on mac m1, the dump file cannot be generated after the application is packaged, but it can be generated in the development environment.

[cuijindong]

🤔 Could you try adding the following snippet to your main process code, before app.whenReady? It's similar to the code you linked above, but pair down the variables to submitURL and uploadToServer, and log the crashDumps path. Make sure this code goes before app.whenReady:

const { app, crashReporter } = require('electron')

console.log(app.getPath('crashDumps'))
crashReporter.start({ submitURL: '', uploadToServer: false })

Then reproduce the crash. Let me know if that is still not working.

You can package the following code and test it on mac m1, and you will be able to reproduce the problem I mentioned: the dump file cannot be generated.

const { app, crashReporter } = require('electron')

console.log(app.getPath('crashDumps'))
crashReporter.start({ submitURL: '', uploadToServer: false })

setTimeout(() => {
  process.crash()
}, 3000);