-
James Juran authored
could happen if the emulator initialization failed for some reason and the drivers hadn't been initialized yet.
fcf353f2
could happen if the emulator initialization failed for some reason and the drivers hadn't been initialized yet.