On 01/05/2015 01:03, Michael Roth wrote: > > I played around with the idea of temporarilly moving unparented, unfinalized > objects to an "orphan" container. It seemed like a fun way of tracking leaked > objects, and avoids the assert, but that got wierd pretty quickly... and > having DEVICE_DELETED randomly change up the device path didn't seem like > the intended behavior, so this hack ended up seeming pretty reasonable. > > The other approach, which I hadn't looked into too closely, was to defer > unparenting an object until it's ref count goes to 0. Could maybe look into > that instead if it seems less hacky.
What about unparenting children devices in the device's unrealize callback? It sucks that you have to do it manually, but using stale canonical paths isn't the nicest thing either. Paolo
