Comment 4 for bug 1158278

I haven't been able to reproduce the high cpu usage with the Texdoc scope.
Nevertheless changes have been made to prevent scopes from starting when their local data source is missing.