Community
Participate
Working Groups
Bug: Invocation of java.net.URL.hashCode(), which blocks to do domain name resolution, in org.eclipse.jdt.internal.core.index.IndexLocation.hashCode() The equals and hashCode method of URL perform domain name resolution, this can result in a big performance hit. See http://michaelscharf.blogspot.com/2006/11/javaneturlequals-and-hashcode-make.html for more information. Consider using java.net.URI instead. Rank: Of Concern (16), confidence: High Pattern: DMI_BLOCKING_METHODS_ON_URL Type: Dm, Category: PERFORMANCE (Performance)
More cases in org.eclipse.jdt.internal.core.index.JarIndexLocation.equals(Object) org.eclipse.jdt.internal.core.search.indexing.IndexManager.computeIndexLocation(IPath, URL) org.eclipse.jdt.internal.core.ClasspathChange.requestIndexing()
Gerrit change https://git.eclipse.org/r/c/jdt/eclipse.jdt.core/+/174169 was merged to [master]. Commit: http://git.eclipse.org/c/jdt/eclipse.jdt.core.git/commit/?id=668dc1ad8dd4dcf5e69c83b9697df1b556fc20b5
New Gerrit change created: https://git.eclipse.org/r/c/jdt/eclipse.jdt.core/+/192601
See https://github.com/eclipse-jdt/eclipse.jdt.core/issues/235. This change caused regressions and I had to partly revert it.