In the segfetcher loop we first resolve segments and check the NextQuery table to see what is cached. Then we request missing data. If multiple core request are done and revocations are involved it can happen that the NextQuery entry for an already requested core segment is deleted. So in the next resolve phase the request is again identified as to be fetched.

To prevent this we should make sure that for each segment type we only fetch once per path request.