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

chore: remove no_stack_dumping.patch #15785

Merged
merged 1 commit into from
Nov 21, 2018
Merged

Conversation

nornagon
Copy link
Member

we build with IS_OFFICIAL_BUILD now so this should be OK

Release Notes

Notes: no-notes

we build with IS_OFFICIAL_BUILD now so this should be OK
@nornagon nornagon requested a review from a team November 20, 2018 22:56
@codebytere codebytere merged commit 65099ab into master Nov 21, 2018
@release-clerk
Copy link

release-clerk bot commented Nov 21, 2018

No Release Notes

@codebytere codebytere deleted the remove-no_stack_dumping.patch branch November 21, 2018 04:32
@deepak1556
Copy link
Member

deepak1556 commented Nov 21, 2018

This enables stack dumping in non-official builds, and it seems we don't want them in arm for certain crash https://github.com/electron/electron/blob/master/atom/app/atom_main_delegate.cc#L159-L170 ? Should that be removed now ? FWIW, the CI doesn't seem to crash.

@nornagon
Copy link
Member Author

If this causes an issue in debug mode on certain architectures we can disable it with --disable-in-process-stack-traces instead of a chrome patch.

@deepak1556
Copy link
Member

Yes, the code in https://github.com/electron/electron/blob/master/atom/app/atom_main_delegate.cc#L159-L170 , should be simplified now, as its redundant for non-official builds.

nornagon added a commit that referenced this pull request Nov 29, 2018
bcpete pushed a commit to bcpete/electron that referenced this pull request Apr 18, 2019
we build with IS_OFFICIAL_BUILD now so this should be OK
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants