TryBugHunt
javaLogic errorMedium

HashMap lookup fails due to missing hashCode

BugFind the bug and fix the code

What it should do

Store and retrieve user record from HashMap. Example: cacheUserRecord("Alice") -> 100

What happens instead

map.get(new UserKey("Alice")) returns null because hashCode is not overridden

import java.util.HashMap;
import java.util.Map;
import java.util.Objects;

class UserKey {
    String username;
    UserKey(String u) { this.username = u; }
    
    // Overrides equals but NOT hashCode!
    @Override
    public boolean equals(Object o) {
        if (this == o) return true;
        if (o == null || getClass() != o.getClass()) return false;
        UserKey userKey = (UserKey) o;
        return Objects.equals(username, userKey.username);
    }
}

public class Main {
    public static int cacheUserRecord(String username) {
        Map<UserKey, Integer> map = new HashMap<>();
        map.put(new UserKey(username), 100);
        // Lookup creates new UserKey instance with different default identity hashCode
        Integer val = map.get(new UserKey(username));
        return val != null ? val : -1;
    }

    public static void main(String[] args) {
        System.out.println(cacheUserRecord("Alice"));
    }
}

Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).

⏱️0:00
Hints
🏆 0 hints = Flawless Solve
Think & Test Cooldown
2:00 remaining

Take a moment to read the bug symptom and trace the code with Run & Check before unlocking Hint 1.

Hint 2
Unlocks after Hint 1
Hint 3
Unlocks after Hint 2

This bug belongs to the logic errors pattern

The wrong operator, an inverted condition, a formula the right way round but backwards.

What you'll practise

A medium Java debugging exercise about logic errors: the wrong operator, an inverted condition, a formula the right way round but backwards.

The checks your fix must pass

Signs of this kind of bug

Spoiler: why this bug happens(try it first; the hints get warmer one at a time)

What went wrong: Java's equals and hashCode contract states that if two objects are equal according to equals(), they must produce the exact same hashCode(). Without overriding hashCode(), HashMap looks in the wrong bucket and fails to find the entry.

The fix: Override hashCode() to return Objects.hash(username).

Remember: Whenever you override equals() in Java, you MUST also override hashCode().

The pattern behind it: logic errors.

More logic errors to practise

Embed this challenge on your site

Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.

<iframe src="https://trybughunt.com/embed/2d1ef838-f1d1-4773-8846-e7d8fd469ae2" title="Debugging challenge: HashMap lookup fails due to missing hashCode" width="100%" height="580" loading="lazy" style="border:1px solid #d4d4d8;border-radius:12px;max-width:760px"></iframe>
<p style="font-size:14px">Debugging challenge from <a href="https://trybughunt.com/challenges/2d1ef838-f1d1-4773-8846-e7d8fd469ae2">TryBugHunt</a></p>