PYQT5 QThread: Destroyed while thread is still running

Yok0

@JonB Yeah your right, but at that point I thought I needed it, but in my case it is useless and as @SGaist mentioned it, QProcess is already async. Before posting this message I used to get the error QProcess / Qthread destroyed while... and I did not fully understood that error. After refactoring my code everything works perfectly!

@SGaist my mistake, indeed QProcess is already async, I guess the issue was how my code was organised.

JonB

@Yok0 said in PYQT5 QThread: Destroyed while thread is still running:

QProcess / Qthread destroyed while

You get this when you set off a process, don't wait for it finish, and let the QProcess variable go out of scope. It needs to persist as long as the process is running. So e.g.

void someFunction()
{
    QProcess proc;    // local, stack variable
    proc.start(...);    // start process, but it hasn't yet finished
    // exiting here will destroy the `proc` variable
    // since the process is running, you'll get the " QProcess / Qthread destroyed while ..."
}

Yok0

Sorry @JonB and @SGaist but I have another question. I'ts not directly linked with QProcess but it's a general question about packaging. Now that's my app running great I packed it with fbs. With the command "fbs run", my app runs fine so I "fbs freeze" it.
The app shows up, everything working but when my QProcess get's called nothing happens.

SGaist

What are you calling from QProcess ?

Yok0

This post is deleted!

Yok0

EDIT : soooo Stupid...
@SGaist when you asked what I was calling it gave me an idea. I changed my command with an os based one like "ls -l" and it worked. I thought it was the same with my cli app I was calling. So i just threw it like QProcess.start("someapp arg").
To make it work I just had to specify the absolute path like QProcess.start("/usr/local/bin/someapp arg").

Sorry for that and @SGaist thanks for your assistance!

SGaist

Rather than hard coding such a path, you might want to consider modifying the PATH environment variable using QProcessEnvironment so that you don't rely on where it could be exactly and also provide the option for your users to change the path where that application can be found.

Yok0

@SGaist sure QProcessEnvironment is a better way.
Also, I thought I could find the path programmatically like using shutil.which("app") but when the program is bundled and launched from the myApp.app. shutil.which() can't find program in /usr/local... it only find os based executable like ls.

SGaist

How are you bundling it ?
Is it a compiled executable ?

Yok0

I use fbs to package it for macos, it gives me an executable myApp.app

SGaist

I meant the application you execute with QProcess.

Yok0

Oh it's youtube-dl and it's work fine like I said if I specify the absolute path of the executable in this case it's /usr/local/bin/...
Sorry it's not related to QProcess but in some situations youtube-dl needs ffmpeg so I would check if it's installed on the system. That's why I use shutil.which('ffmpeg').
It works great in my virtualenv but after compiled the program, shutil can't find the path of ffmpeg. Somehow it can't find apps in /usr/local/bin even if it is in $PATH. However it will find os based app like "ls", "mkdir"...

JonB

@Yok0
Are you certain /usr/local/bin is on your PATH, really? Things like ls/mkdir are in /bin and/or /usr/bin, which will be on $PATH, maybe /usr/local/bin is not.

Yok0

@JonB Yep! I did checked it.
In my app I tried to displayed my $PATH with os.environ.get('PATH'). When I run it in my virtualenv, it shows me to correct $PATH with /usr/bin, /usr/bin/local/, .cargo/bin so on and so forth BUT after bundling the project in an executable, that same command only returns /usr/bin:/bin:/usr/sbin:/sbin
The weird thing is that the app is run by the same user in venv and as a executable. The $PATH is somehow overridden.

JonB

@Yok0
Yes, virtualenv's job is to set your path. It is not surprising it is different from path outside venv.

So your problem is that the executable you wish to run lives in a directory which is not on your usual path.

Yok0

@JonB mhm indeed the working direcory of the executable become /
instead of /Users/foo .. obvious, thanks.

JonB

@Yok0
You're not executing this as root/su on the installed system, are you?

Yok0

@JonB nop regular user

JonB

@Yok0
Then there's something "odd" about / being the working directory! The whole thing might make sense as root, as he may not have /usr/local/bin on his PATH.