[Bug]: Freetube always ignores --disable-crashpad

[minionaire]

Guidelines

• [X] I have encountered this bug in the latest release of FreeTube.
• [X] I have searched the issue tracker for a bug report that matches the one I want to file, without success.
• [X] I have searched the documentation for information that matches the description of the bug I want to file, without success.

Describe the bug

Ubuntu: Go to /opt/Freetube/freetube Add --disable-crashpad to the executable Launch Freetube Open any system monitor Find the process still running somehow.

Expected Behavior

No crashpad related process is expected

Issue Labels

usability issue

FreeTube Version

v0.16.0

Operating System Version

Ubuntu 22.04

Installation Method (If applicable)

.deb

Last Known Working FreeTube Version (If Any)

No response

Primary API used

No response

Additional Information

No response

Nightly Build

• [ ] I have encountered this bug in the latest nightly build.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[ChunkyProgrammer]

I am not familiar with crash pad but we do not do any configuration for it so this may be an electron issue?

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[efb4f5ff-1298-471a-8973-3d47447115dc]

hi @minionaire could you try the latest nightly build and report back if this behavior is fixed

[minionaire]

hi @minionaire could you try the latest nightly build and report back if this behavior is fixed

Alright, I will do that. The build is buried so deep though.

[minionaire]

Before: 0.19.1 Beta

After:0.19.1 Nightly 4044

Observation: Idle memory consumption for all Freetube processes is at ~172MB now compared to 169MB earlier. The crashpad handler file is much smaller now. Saves disk space.

[efb4f5ff-1298-471a-8973-3d47447115dc]

I am not familiar with crash pad. Are you saying the behavior is fixed or that this is an unrelated observation you made about the process size

[minionaire]

It is an issue that plagues most wrappers and chromium browsers on Linux. Privacy concern for some and bloat for others.

Check out these threads where people face the same issue. https://community.brave.com/t/start-brave-without-enable-crashpad/305072

https://github.com/signalapp/Signal-Desktop/issues/5963

I simply noticed that the executable responsible for crash handling is smaller now, but the issue persists.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.