-
Edward Hervey authored
This was going through a few locks and doing temporarily allocations for every single task creation.. just to get a name. We don't need to take locks since: * The parent exists (we have a reference to it) * The pad exists (the task belongs to it) * Changing names of pad/elements when activating is a big no-no Instead use the existing direct GST_DEBUG_PAD_NAME macro Part-of: <!455>
5e553b8c