[Bug]: Error on Startup in FreeTube Version v0.19.0-beta - Issue Reopened

[mathe00]

Guidelines

• [X] I have encountered this bug in the latest release of FreeTube.
• [X] I have encountered this bug in the official downloads of FreeTube.
• [X] I have searched the issue tracker for open and closed issues that are similar to the bug report 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.
• [X] This issue contains only one bug.

Describe the bug

I am encountering an issue at the startup of FreeTube version v0.19.0-beta. When attempting to launch the application, an error window pops up, preventing me from accessing the application. This is the only problem I am experiencing. The other details in the previous report do not apply to my situation.

Steps to Reproduce

1. Attempt to launch FreeTube v0.19.0-beta.
2. An error window immediately appears upon startup, preventing access to the application.

Notes

I want to clarify that this issue occurs during the application's startup. Unlike the previous report, I cannot access the application interface. This situation renders the normal use of FreeTube impossible.

I kindly request the development team to reopen this issue for investigation and resolution of this startup problem, allowing users to enjoy the application without encountering blockages.

Thank you for taking these details into consideration.

Expected Behavior

I expected FreeTube v0.19.0-beta to launch without any errors, allowing me to access and use the application normally.

Issue Labels

causes crash, inconsistent behavior, usability issue

FreeTube Version

v0.19.0-beta

Operating System Version

Manjaro Linux, Kernel 6.1.44-1-MANJARO (64-bit)

Installation Method

AUR

Primary API used

Local API

Last Known Working FreeTube Version (If Any)

No response

Additional Information

The issue occurs at the application's startup, displaying an error window that prevents me from accessing FreeTube. This situation renders the application unusable. Here is the link to the related original issue: GitHub Issue Link

Nightly Build

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

[absidue]

You ticked the box saying you encountered it in one of the official releases, but then listed your installation method as AUR, which is an unofficial release. Did you actually test it on an official release too or just AUR?

Additionally please provide a screenshot of the error, we can't really investigate anything without any information to go off.

[mathe00]

Since my installation with AUR

By launching the AppImage just after

I actually installed it from the AUR, apologies for the error. I've just downloaded the AppImage and encountered the same error as when trying to launch Freetube installed with the AUR.

[absidue]

Did you remove the AUR install before installing the AppImage? unless you installed the AppImage into the exact same file system location as the AUR package, the second screenshot is still from the AUR install in /opt/FreeTube.

As for the error itself, definitely a weird one, as it's happening inside the handler for when you launch a second instance of FreeTube (see cursor next to isMinimized on the left side): https://github.com/FreeTubeApp/FreeTube/blob/f4cee17b136e6339244fa686ad0f11eca8326f6b/src/main/index.js#L207

[absidue]

As you seem to be the only person with this issue at the moment, this doesn't sound like an issue in FreeTube itself, as the users on the previous issue seemed to be using arch/manjaro too, I suspect this is an operating/setup specific issue (never had anything like that in my years of using FreeTube on Windows).

Could you try checking if you have any instances of FreeTube running in your task manger/process viewer, if yes kill them and try again? (my only guess at the moment is that the your linux setup is closing the window, but not actually ending the process, so when you "start" it again, it tries to access the old window, but that has been removed by the operating system/window manager)

[mathe00]

Indeed, when I launch FreeTube, I have all these processes running. And when I close FreeTube, only one of these processes closes. And to answer your first question, no I hadn't uninstalled the AUR version before trying AppImage, please excuse me.

[Garpgarp]

Hi, non-technical user here that had presumably a very similar issue on Fedora, but I hope it can help the OP.

Managed to get things up and running by making backups of whatever Freetube labelled folders I could find under home directory (~/.var/io.freetubeapp.FreeTube and ~/.config/Freetube) then deleting those folders, and running the following commands based on what I could find on Google:

dnf history userinstalled dnf remove freetube-0.19.0-1.x86_64

Opted to reinstall using the official flatpak and after reimporting my history from the folder backups we're up and running.

[absidue]

Very odd that it is happening but glad that a full reinstall fixes it.

Sounds like thing get handled properly with the flatpak version but fail when running without flatpak. Makes me think the issue is outside of FreeTube but this is Linux, so it could be caused by anything.

[mathe00]

I had the problem again with another fresh installation of Linux Manjaro, but this time no installation via the AUR, it's the AppImage installation. I'm just saying that to let everyone know that it's not AUR specific. So I do pkill freetube as soon as I encounter this problem, it's a quick and efficient way to temporarily fix the problem.

[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.

[dcstraney]

Encountered this same error in Windows 11 / x64 with 0.19.1. Sometimes would happen randomly and after re-trying later would work correctly, but today was consistently showing the same "object destroyed" message each time. Installing the latest nightly build (3610) fixed it, but will see how long that lasts, or if that was just a roundabout fix to a "leftover processes" problem (unfortunately installed nightly before seeing this thread). If I see the same error again will have to check the process list - will report back.

[dcstraney]

With nightly build 3610, however, I did still see FreeTube processes after closing the FreeTube window: FreeTube still launched a second and third time correctly though, and both times after closing the window, all its processes disappeared over the course of ~10 seconds, whether on the Subscriptions screen or in the middle of a video - so this seems to be intermittent.

[absidue]

Processes existing for a while after you've closed the last window is expected, as FreeTube has to do some cleanup to avoid data corruption issues that were happening in the past (previously FreeTube tried to do it, but because the processes were shutting down before it was finished, occasionally it would result in your data getting corrupted).

[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.

[PABERTHIER]

Having the same issue with a fresh install from yesterday (latest version). Windows 10, Version 22H2 (OS Build 19045.4046).

Once the soft has been shut down, no way to reopen it without a computer restart. I understand the thing about processes, but maybe something has be to be done about handling them to prevent these issues and without risking the data corruption. Or maybe at least something to warn the user for example ?

PS: Insane work for this software, love it so far ! U guys are monsters !

[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]

@mathe00 do you still face this issue on V0.20.0?

[mathe00]

@mathe00 do you still face this issue on V0.20.0?

No, I haven't had any problems whatsoever with Freetube for a long time now.