microsoft / microsoft/OmniParser
Omniparser crashes after processing 7 images.
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 25.4k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
2024-12-04 23:44:04 finish processing
2024-12-04 23:44:04
2024-12-04 23:44:04 image 1/1 /usr/src/app/imgs/saved_image_demo.png: 384x640 122 0s, 31.8ms
2024-12-04 23:44:04 Speed: 3.9ms preprocess, 31.8ms inference, 2.3ms postprocess per image at shape (1, 3, 384, 640)
2024-12-04 23:44:33 finish processing
2024-12-04 23:44:33
2024-12-04 23:44:33 image 1/1 /usr/src/app/imgs/saved_image_demo.png: 384x640 119 0s, 31.7ms
2024-12-04 23:44:33 Speed: 4.1ms preprocess, 31.7ms inference, 2.1ms postprocess per image at shape (1, 3, 384, 640)
2024-12-04 23:45:10 /usr/src/app/entrypoint.sh: line 8: 7 Killed python ./gradio_demo.py
Why does this occur. I am running omniparser locally via docker.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with entrypoint.sh line 8 and gradio_demo.py, then reproduce the crash in the local Docker setup while processing images. Check the container and process behavior around the seventh image; the work is done when the cause of the process being killed is identified and a verified resolution or clear diagnosis is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- computer-vision, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100