search

alex-moon / vc

MIT License
22 stars 6 forks source link

Hanging forever on inpainting? #47

Open alex-moon opened 2 years ago

alex-moon commented 2 years ago

Recently it seems the worker can get stuck doing 3D Photo Inpainting - it apparently stays at 35% memory and 100% CPU for over 30 minutes, as though in a tight loop. Why?

alex-moon commented 2 years ago

OK we have an example. This also happens to be the thing that chokes the PC making it unusable. Here's debugging output:

2021-12-11T21:17:30: DEBUG: GenerationRunner inpainting handle
2021-12-11T21:17:30: DEBUG: GenerationRunner inpainting load_ply False
2021-12-11T21:17:30: DEBUG: InpaintingService running on device cuda
2021-12-11T21:17:30: DEBUG: InpaintingService current source output
2021-12-11T21:17:30: DEBUG: InpaintingService Running depth extraction
2021-12-11T21:17:30: DEBUG: midas initialize
2021-12-11T21:17:30: DEBUG: midas device cuda
2021-12-11T21:17:34: DEBUG: midas processing output.png
2021-12-11T21:17:34: DEBUG: midas writing /opt/vc/depth/output
2021-12-11T21:17:34: DEBUG: midas finished
2021-12-11T21:17:37: DEBUG: InpaintingService Start Running 3D_Photo cuda
2021-12-11T21:17:37: DEBUG: InpaintingService Loading edge model
2021-12-11T21:17:38: DEBUG: InpaintingService Loading depth model
2021-12-11T21:17:39: DEBUG: InpaintingService Loading rgb model
2021-12-11T21:17:40: DEBUG: InpaintingService Writing depth ply (and basically doing everything)
2021-12-11T21:27:59: LOG: Writing mesh file mesh/output.ply ...
2021-12-11T21:35:25: DEBUG: InpaintingService Making inpainting frame
2021-12-11T21:35:25: LOG: fov: 53.13010235415598
2021-12-11T21:35:26: LOG: mesh.py Writing Inpainting output frame: /opt/vc/output.png
2021-12-11T21:35:26: DEBUG: Inpainting took 0h 17m 56s
alex-moon commented 2 years ago

OK so one thing: 3PI is a rat's nest. There is another option: try a different AI here, e.g. this one: https://github.com/CompVis/geometry-free-view-synthesis