a pretty bad bug report about a segfault, but at least I can show you the repo

I am at a bit of a loss as to what happened here, because I just noticed my editor's inline type-checking suddenly went away, and then saw a mypy process consuming an entire core for multiple minutes at a time, then crashing. I figured I'd get the report in quickly rather than try to minimize first, but I understand this is a pretty poor-quality bug report. The fact that the repo is open source might make it easy enough to get into a debugger for someone more knowledgeable.

Crash Report

zsh: segmentation fault mypy src

Traceback

it's a segfault so --show-traceback gives me nothing.

To Reproduce

mypy src on
https://github.com/glyph/Pomodouroboros/pull/69/commits/8a8102c16ad7171508c2825c78af7f2f337dc9a7

Your Environment

• Mypy version used: mypy 1.13.0 (compiled: yes)
• Mypy command-line flags: none
• Mypy configuration options from mypy.ini (and other config files): see repo
• Python version used: 3.12.7
• Operating system and version:

ProductName:		macOS
ProductVersion:		15.1.1
BuildVersion:		24B91

Check out the linked Pomodouroboros commit and first run mypy src with the reported Python and mypy versions to confirm the segmentation fault. Use a debugger to identify the failing path and trace the crash to a reproducible cause. Done means the command no longer segfaults on this repository and the regression is covered by an appropriate test.