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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

convert is keeping a subprocess or thread running after returning results #915

Closed
patw opened this issue Feb 7, 2025 · 1 comment
Closed
Labels
bug Something isn't working

Comments

@patw
Copy link

patw commented Feb 7, 2025

Bug

I wrapped docling in a fastapi service, and noticed that after running any of the endpoints that include convert that the cpu would spin up to convert doc, but something continues to run in the background (single core, 100% cpu -- no idea what it is).
...

Steps to reproduce

Run the convert function on a PDF doc then just pause execution. Run top command and you should see something lingering on the same process ID consuming a cpu core.

Can be seen running this: https://github.com/patw/docinator
...

Docling version

docling 2.18.0
docling-core 2.17.2
docling-ibm-models 3.3.1
docling-parse 3.1.0
...

Python version

3.10.12 running under Ubuntu 22.04
...

@patw patw added the bug Something isn't working label Feb 7, 2025
@dolfim-ibm
Copy link
Contributor

We usually support only the docling-serve REST API for Docling, we are trying to centralize all the work there. If you see that your use case is not covered or planned, we are happy to know about it.

I suggest you reopen the issue if you notice the same behavior in docling-serve.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants