excellent report thank. this is about what i expect. whats important is that it is not reaching 10-20 meg range. i left it running for about 10 min and it had hit the 20 meggerbytes mark

In my case, I tried the 32 bit version of Wabbitemu on my 64 bit install of Windows 7 and it sat at 6552 for 10 minutes. It has never changed since I started it up.

EDIT: Now it went down to 6524 then 6496 then 6460. I'll leave it open while at work.

Ok, to update my last post, when I returned from work after 7 hours, WabbitEmu took 6476 KB

EDIT: Problemo: In both 32 and 64 bit builds of Wabbitemu, screenshoting with autosave enabled no longer works. In both cases, when I start capturing, I get an error sayign the program has stopped working and must close in Windows 7 64 bit edition.

When auto-save is disabled, it works, but when stopping capture, in some cases, it prompts the save as window again, like if I was starting the capture. This happened in the 2007 build I think, but was fixed a long while ago. It just re-appeared now.

Hmm what type of files are you exporting? How big were they? If you can provide an example it could help me track it down. I'm guessing they were apps, since the other file exporting code hasnt really changed

So apparently there have been some complaints lately about wabbitemu running faster than normal. Its entirely possible that in my mucking in the calc_run_all code that i made a mistake and made it run faster than should. So naturally i did some testing. First, all tests were on the following calc (and a rom of the same calc):
TI-84+SE from 2006 (hardware revision F)
OS 2.43
Boot code 1.02

I tested using the a fresh release build (which you guys don't have yet, but there are no differences to the timer code)
I tested using Dr Dnar's stopwatch program. I ran each test twice for accurate results. For testing i ran the prog on each then when both were ready and held my calc up to the comp screen to watch as the timer ran. This way i could see roughly how close they were to start. In 20 seconds there was no noticable difference between the emulator and the calc. I also ran the program for 300 seconds (5 mins). By the end the emu was approximately .5 seconds behind the real calc.
If you guys want to run the same tests, be my guests. I will also accquire some calcs from people on my floor and run the same tests. The ti83+ is probably the most important other one to test, because it doesnt have crystal timers. Make sure the batteries in it are fresh when you test

tl;dr: There is no time difference you guys could notice from just running a normal program.

I did not recreate the export bug, could you send me an example prog? If that doesnt work i'll bug you on irc more

Strange, lots of people mentionned Wabbitemu recently ran faster . Maybe one of the build had a bug that affected other stuff such as the speed but it was accidentally fixed quickly and those people still had that version. Not sure.