RangeError Threshold Confusion in Python json module deep parsing

The precise goal is to determine how Python's json module handles JSON input that triggers a RangeError due to excessive nesting, and whether this error can be reliably distinguished from a caller-enforced timeout. In single-threaded runtimes, json.loads() blocks the event loop indefinitely, so a setTimeout wrapper may expire while the parser remains active, producing an ambiguous execution state where the exception type does not clearly signal timeout versus depth exhaustion.

Documentation indicates that RangeError stems from C-level stack overflow during parsing of deeply nested structures, but the threshold behavior across Python versions (3.8 through 3.12) and the efficacy of cancellation callbacks or async streaming alternatives are not firmly established.

How does the RangeError threshold vary with interpreter build and memory configuration? Can an application-level timeout reliably interrupt a blocking json.loads() call without corrupting interpreter state? What mechanisms, if any, enable graceful error mapping when parse termination results from stack depth exhaustion versus time expiration?