Blitter can crash when switching from level 0 to level 2 when the emulator is running.

Presumably fixed in vAmiga 0.43
Activity monitoring has been implemented in this release, too:

My new love is this activity monitor thing. It is fun to look at demos or games and to learn how they are using the Amiga. And it looks so nice.馃槏
While playing with it, I did asked me why can't we display the CPU activity as well, like in the activity monitor of macos?
Then I instantly rejected my question because I thought that it is maybe not possible to let the old 68k CPU do nothing.馃ゴ But I remembered that there was a special 68k command.
NOP
Execution continues with the instruction following the NOP instruction. The NOP instruction does not begin execution until all pending bus cycles are completed.
Count all commands as activity except NOP ? My guess is that the CPU would always show 100%.馃槴馃お
What the heck is the macos CPU activity monitor showing us ? Maybe it counts only the bus activity? 馃え
What about this strategy: Whenever the 68k-CPU accesses memory there is CPU (bus)-activity, we could count that. Or maybe it is even better to count only CPU writes to the memory as activity? This way we could blame games which are moving graphical objects with CPU instead of the blitter.馃檭
Most helpful comment
Presumably fixed in vAmiga 0.43
Activity monitoring has been implemented in this release, too: