Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Crash Reporting/Crash Reporter #169

Open
Bioblaze opened this issue Dec 2, 2024 · 2 comments
Open

Add Crash Reporting/Crash Reporter #169

Bioblaze opened this issue Dec 2, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@Bioblaze
Copy link

Bioblaze commented Dec 2, 2024

https://github.com/chromium/crashpad?tab=readme-ov-file
https://github.com/google/breakpad

@Bioblaze Bioblaze converted this from a draft issue Dec 2, 2024
@Splizard
Copy link

Splizard commented Dec 2, 2024

Not familiar with the aforementioned projects but I was wondering if something like Sentry would be a good fit for consuming the crash reports, they have a free self hosted option. For the engine itself, it could be useful to have the information publicly accessible.

You would probably want a way to differentiate between crashes caused by code written by the game developer (which resorts should go to them) versus engine crashes. Maybe they can be triaged and forwarded, can this be deduced from stack traces?

@Ughuuu
Copy link

Ughuuu commented Dec 2, 2024

The client that is used to send this data should be configurable as for the server, offering indeed popular options, but also self hosted if people want.
Initially we would want to collect this data, and then have an easy way to specify how this data is uploaded.
If it were to sentry, while maybe industry standard? maybe not, idk, we have to consider also to not lock people in to one option, and offer them option to again self host and receive this data (if they want to)

@jss2a98aj jss2a98aj added the enhancement New feature or request label Dec 7, 2024
@Bioblaze Bioblaze moved this to Backlog in Blazium Engine Roadmap Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

4 participants