Closed floooh closed 8 years ago
Fixed, reason was that the abs_cycle_count was not reset on z1013::poweron(), and the freeze didn't happen on the first time (since then abs_cycle_count was always 0 und was initialized with min_cycle_count), but for followup-boots, in this case, abs_cycle_count wasn't set to min_cycle_count and thus tried to catch up in the first frame.
Repro: hang around in the KC85/4 emulation for several minutes, than switch to Z1013, this can freeze the emulator for several seconds. Is there something wrong with the min/max-cycle count computation, so that the z1013 runs a lot of cycles in the first frame to 'catch up'? Something not reset on poweron?