Fix use-after-free in submodule reload
If the first call to release a no-longer-existent submodule freed the object, the check if a second is needed would dereference the data that was just freed.
Showing
Please
register
or
sign in
to comment