What closes the program? If you have 1000 instances of the same program in memory then it’s quite likely you will run into memory issues. If the app launches and then exits quickly then try adding a short delay in the loop.
If the application is yours then you might want to think about altering it so that it can do everything you need in one invocation. If it’s a gui app (which it looks like it is), create a console version that does the processing you need, console apps take a fraction of the resources (handles etc) that gui applications take.
Another thing, if you are running on a 32bit machine, try running on a 64bit machine… each process will get it’s own 2Gb address space and I believe 64bit windows allows more global handles etc.
Hi;
Thanks for your quick reply. I am running the same test by running notepad.exe. After running 1200 times I stop the final builder by stop button and the bug at the attachemnt occurs. Do you have any idea about this bug report?
bugreport.txt and notepad.fbz7 are at the attechement.
Regards.
004_003_002_001_bugreport.txt (155.674 KB)notepad.fbz7 (2.629 KB)The bug report is the same as the one you posted before, it’s most likely caused by a corrupt log file, which is itself caused by the previous crashes. The fix is to rename the log file (C:\FinalBuilder\Test Projects\AnaModül\OTF_CLOSE ACTIVEPROJECT.fbl6) so that FinalBuilder creates a new one.
BTW, Running notepad proves nothing, it’s a very small low resource using application.
Posted By Vincent Parrett on 09 Jun 2011 03:56 AM
Another thing, if you are running on a 32bit machine, try running on a 64bit machine.. each process will get it's own 2Gb address space and I believe 64bit windows allows more global handles etc.
Do I run final builder on 64 bit windows?
Yes, that is what I would suggest in this case.