Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Puzzle Bank
  • SystemVerilog Language Puzzles25
  • Difficulty Guide
  • Full Topic Map
  • Interview-Day Tips
  • OOP & Testbench Puzzles25
  • Concurrency & Timing Puzzles25
  • Randomization & Constraint Puzzles25
  • SVA Assertion Puzzles25
  • Functional Coverage Puzzles25
  • Logic & Aptitude Puzzles25
    • Classic Brain Teasers
    • Probability Puzzles
    • Digital Logic Puzzles
    • Debugging Riddles
      • Scoreboard Sees Previous-Cycle Data
      • Reset Release Causes Occasional X State
      • always_comb with NBA and Missing Else
      • UVM Analysis Port Handle Reuse
      • join_any Timeout Ghost Thread
      • Randomization Always Fails: Hidden Unsat
    • Logic & Aptitude Puzzles: Tricky Q&A
  • Scenario & Debug Puzzles25
  • Interview Prep: Puzzle Rounds5
  • DV Puzzle Cheatsheet
Loading lesson

‹Debugging Riddles
  1. Topics
  2. DV Interview Puzzles
  3. Logic & Aptitude Puzzles
  4. Debugging Riddles
  5. join_any Timeout Ghost Thread

VLSI DV Interview Puzzles · All levels

join_any Timeout Ghost Thread

A test sometimes passes then later crashes with timeout fatal. Why can this happen?

On this page

    Puzzle

    Difficulty: Medium · Puzzle 5 of 6 · Topic: Debugging Riddles

    A test sometimes passes then later crashes with timeout fatal. Why can this happen?

    Code

    design.sv
    1
    2
    3
    4
    5
    6
    7
    8
    9
    fork
      begin
        wait(done);
      end
      begin
        #1000 `uvm_fatal("TIMEOUT", "No completion")
      end
    join_any
    // missing disable fork

    Hint

    What happens to the losing forked branch after join_any?

    Step-by-step solution

    Diagram
    1) join_any returns when first branch finishes (e.g., done becomes true).
    2) Other branch keeps running unless explicitly killed.
    3) Timeout branch later reaches #1000 and calls fatal, even though operation succeeded.
    4) Add disable fork immediately after join_any, or use structured timeout utility that cancels losing branch.

    Answer

    Answer: Missing `disable fork` leaves timeout thread alive; it fires later as a false fatal.

    Why candidates get it wrong

    Believing join_any automatically terminates other branches.

    Interviewer follow-up

    How would you write the same logic using `process` handles for explicit kill?

    Related topics

    • Back to Debugging Riddles

    • Logic & Aptitude Puzzles section

    Previous

    177 / 210

    Next: Randomization Always Fails: Hidden Unsat

    Up next

    Up nextRandomization Always Fails: Hidden Unsat

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Scoreboard Sees Previous-Cycle Data
    • Reset Release Causes Occasional X State
    • always_comb with NBA and Missing Else