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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Abandoning a job does not cancel transcoding #1014

Open
4 tasks done
stevenvergenz opened this issue Dec 15, 2023 · 2 comments
Open
4 tasks done

馃悰 Abandoning a job does not cancel transcoding #1014

stevenvergenz opened this issue Dec 15, 2023 · 2 comments
Labels
bug Contains a bug or code error
Milestone

Comments

@stevenvergenz
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

I have checked the wiki

  • I have searched the wiki for this problem

Does this issue exist in the latest version?

  • I'm using the latest release

Describe the bug?

After clicking "Abandon Job" in the UI, the job gets marked as abandoned, but the transcoding continues in the background with no way to stop it in the tool.

To Reproduce

  1. Start a DVD or Bluray ripping
  2. Wait for it to reach the transcoding stage
  3. Abandon the job
  4. Observe the transcode continuing (high CPU usage, counts against transcode limit, etc.)

What OS are you seeing the problem on?

Other (please state in Anything else? section)

ARM Release Version or Git hash (You can find this in the arm settings page)

2.6.67

Expected behavior?

The transcode is canceled when the job is abandoned.

Relevant log output

No response

Anything else?

Docker image running on Fedora Server host

Code of Conduct

  • I agree to follow this project's Code of Conduct
@stevenvergenz stevenvergenz added the bug Contains a bug or code error label Dec 15, 2023
@Zackptg5
Copy link
Contributor

Same issue here on latest 2.6.71 release. When trying to cancel a job, it says "Couldn't find job.pid - XXXXX! Reverting db changes."

@microtechno9000
Copy link
Collaborator

Thanks for raising, there are a few bugs like this with the ripping process. We are working on rewriting a lot of the ARM modules at the moment to make the code cleaner and easier to resolve bugs like this.

@microtechno9000 microtechno9000 added this to the 3.0 milestone Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Contains a bug or code error
Projects
Status: Todo
Development

No branches or pull requests

3 participants