Closed Neyl-123 closed 1 month ago
The 'Failed to connect to the bus' is exclusive to FreeTube.
As the logs around that seem to be things about not being able to access the system theme, it's probably not related to the crash itself.
As for the crash itself that is definitely concerning, however as it seems to be happening with other flatpak apps that also use Electron, it's probably a problem with flatpak or Electron. So unlikely to be something that the FreeTube devs can fix, but I'll do some research, to see if there are any other people with the same problem and whether the flatpak and/or Electron devs are aware of the problem.
It actually not only happens on the first start, also sometimes when opening a new window
@bbhtt do you maybe have some more insight in this?
Probably an issue in Chromium https://issues.chromium.org/issues/350117526 related to SELinux so Fedora is affected. You should ask Electron developers to see if a fixed Electron version exists or backport any patches.
From giving the linked thread and the links inside that thread a quick read through, it seems to be a Fedora issue and they seem to be reverting one of their changes which caused the problem:
It sounds like there is not much we can do from our side other than wait for either Fedora to undo their change and release it or for Chromium or v8 to come up with a workaround.
Closing as mentioned above we cant do anything about this
Guidelines
Describe the bug
As the Title states, FreeTube often crashes right away on the first start. The out of memory part (see logs below) also occurs with Discord and Signal (both Flatpaks). Which seems to be caused by the V8 Engine going out of memory during initialization (it happens when there is 4GB of RAM available). The 'Failed to connect to the bus' is exclusive to FreeTube.
Expected Behavior
It should not crash
Issue Labels
causes crash
FreeTube Version
v0.21.3 Beta
Operating System Version
Fedora 40 Workstation
Installation Method
Flathub
Primary API used
Local API
Last Known Working FreeTube Version (If Any)
No response
Additional Information
The different logs from GNOME ABRT (in no particular order):
Crash 1
Crash 2
Crash 3
Crash 4
Nightly Build