Darwinbots Forum

Code center => Bugs and fixes => Topic started by: Peter on November 26, 2007, 11:36:32 AM

Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 26, 2007, 11:36:32 AM
Ok, any time I start darwinbots 2.44t I get some errors. Bitmap attached, the upper error is the one I inmidiatly get after starting the program, the program doesn't hang or anything, the second one os the one I get after going to start simulation.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: EricL on November 26, 2007, 12:02:19 PM
Please post your lastexit.sim.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 26, 2007, 01:36:16 PM
Ok, posting sim. And deleting it is taking care of the problem, as I am interested where he gets the sim from it is loading now in the beginning.

It loads somehow a sim
Title: Errors when starting RESOLVED (NO REPRO)
Post by: EricL on November 26, 2007, 01:57:34 PM
When you exit DB, it saves the sim it is running as lastexit.sim.

When you start DB, it loads and runs this sim from the last exit if it exists.  If it does not, it assumes you are a new user.

The lastexit.sim you posted is corrupt.  The error is occurring downstream do to bogus values in the simopts structure.  In particular, a fieldwidth of 0.

Did you have a problem exiting DB the last time before upgrading to 2.43t?  Say, did you turn off the computer before it was done or did windows reboot you overnight installing a patch?

As you have determined, deleting or renaming lastexit.sim will allow you to start and proceed without loading this corrupt save.

Unless you have some idea how the last exit sim became corrupt, this is going to be impossible to repro...
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 26, 2007, 02:15:19 PM
Quote
When you start DB, it loads and runs this sim from the last exit if it exists.  If it does not, it assumes you are a new user.
I know, and I know it starts IM then, but somehow it loaded a sim, and in the whole DB-save-folder there isn't a sim file(I deleted all), the sim it loaded could in fact be the last one. It was the league and I did run the league to have a idea about the bp-size.

Quote
Did you have a problem exiting DB the last time before upgrading to 2.43t?  Say, did you turn off the computer before it was done or did windows reboot you overnight installing a patch?
Could been DB has shut down a few times without a reason, in fact it did shut down just. Still wondering what causes it. And no I didn't turn the computer off before it was done(could be very rare if the harddisk in just in that file cousing an error if it was), new patches aren't installed.

Quote
As you have determined, deleting or renaming lastexit.sim will allow you to start and proceed without loading this corrupt save.
Yep  

Quote
Unless you have some idea how the last exit sim became corrupt, this is going to be impossible to repro...
It probably has to do with one of the times(probably the last) DB shut down. This has happened more often.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: EricL on November 26, 2007, 02:34:41 PM
I'm going to resolve this specific bug as no repro and chalk the sim corruption up to a previous crash.

But I would like to know more about the mysterious DB shutdowns you mention.  Can you open another bug with whatever details you have on that?  How long after running, exactly what do you mean by "shutdown" (I.e. is there still a process in the process list?) and is there is no error dialog? Nothing indicating a crash?  That kind of thing.  Thanks.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 26, 2007, 03:07:06 PM
Somewhy, I don't even know why, I had renamed some of earlier lastexit.sim, all of them are corrupted as appears now.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: EricL on November 26, 2007, 03:15:33 PM
Moved your post to this topic.

Post them if you want.  I'll take a look.

The lastexit.sim you posted above is truncated at bot 108.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 26, 2007, 03:38:34 PM
Ok, I thought you couldn't do anything with the sims.

I deleted most of them, .I had already thrown them in the recycle bin, and before you posted, windows whined about diskspace shortage, lesser than 200mb so I'd empty the recycle bin. Ok, gotta uninstall some stuff.  

One another is left, left in the save-folder here you have it.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: EricL on November 26, 2007, 03:47:34 PM
This one is also truncated (at bot 308 out of 2011).

If you were nearly out of disk space when you exited DB, that would explain this.  It's details like that I need to know...
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 27, 2007, 02:32:44 PM
Well, in fact I was getting and error, later then running DB so I  didn't knew this at the time.  

I am not completely sure about the way windows completely works, but isn't it emptying the recycling a little bin if it really needs the space(there was plenty)  , well so far I am sure I had the same error some time ago too, before the computer was completely full, and have something left like a few gigs.

Oke, I don't know what kind of details I would have to provide you further.

Well I am running windows XP SP2. Well that seems pretty common, so would that help.

Okay further specs.

Celeron 2,6 Ghz
2,59 Ghz, 192MB of Ram

Well okay not a total power computer, and yes it seriously needs ram-memory.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: EricL on November 27, 2007, 03:28:00 PM
Quote from: Peter
I am not completely sure about the way windows completely works, but isn't it emptying the recycling a little bin if it really needs the space(there was plenty)

Windows does not do this.  You must manually empty the recycle bin to free up space.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 27, 2007, 03:40:50 PM
Quote from: EricL
Quote from: Peter
I am not completely sure about the way windows completely works, but isn't it emptying the recycling a little bin if it really needs the space(there was plenty)

Windows does not do this.  You must manually empty the recycle bin to free up space.
Well, okay I did romove the files manuelly, my idea here was if windows uses hard disk space, windows is creating files that are newer and the oldere files are automated removed(as it is if you copy new files to your computer), but okay could be wrong there.

But more importent(or even more useless knowledge)  

The post you just made was the 20000 post.  

 
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Numsgil on November 27, 2007, 03:51:11 PM
Quote from: Peter
Celeron 2,6 Ghz
2,59 Ghz, 192MB of Ram

You have a 2.6 gig processor running with 192 Megs of Ram in XP?  That the computer will even boot boggles my mind.  I didn't even think they made processors for boards that still used 128 and 64 meg RAM cards.  A computer with 2.6 gig processor should have a minimum of 256 - 512 Megs of Ram.  Minimum.  1 - 2 Gigs ram would be optimal.  Just wow.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 27, 2007, 04:24:05 PM
Quote from: Numsgil
Quote from: Peter
Celeron 2,6 Ghz
2,59 Ghz, 192MB of Ram

You have a 2.6 gig processor running with 192 Megs of Ram in XP?  That the computer will even boot boggles my mind.  I didn't even think they made processors for boards that still used 128 and 64 meg RAM cards.  A computer with 2.6 gig processor should have a minimum of 256 - 512 Megs of Ram.  Minimum.  1 - 2 Gigs ram would be optimal.  Just wow.
Just to say it isn't using 128MB and 64MB ram-cards, it has 256 RAM and a 64 onboard videocard.

I know it is low, maybe strange to say but it runs (exept DB) pretty stable, further then windows itself it loads a virusscanner and hamachi and opera(witch has somehow entered the bar)  .It isn't really slowing down or anything, sometimes it is, true.
All the graphic stuff of XP is also shut down, just looks like win95

As it is I know it is too less RAM and instead of the 256MB, I am going to put 1GB(2X 512), it is the maximun the motherboard can take.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: EricL on November 27, 2007, 07:44:32 PM
You void your DB warrenty if you run out of disk space.  Truncated lastexit.sim files are a telling sign that this has happened.   Finding all the places in the code where the the program writes to disk and adding code to detect out of space errors, warn the user and fail gracefully is beyond the scope of the fit and finish work I am willing to do.

Unless some evidence to the contrary arises, I am chalking this bug and probably your sudden shutdown bug up to being out of disk space.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 28, 2007, 05:58:54 AM
Wel okay here you have a sim that is bound to give an error after a while, within 15 minutes. Yes it gave an error, and it sorta hanged afterwards.
I hope you get the error too.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: EricL on November 28, 2007, 11:44:36 AM
I ran the sim.  After 10000 cycles, veggy repopulation attempts to add a single bleednrg as you have specified.  The path on the bot as configured in the sim is C:\Program Files\DarwinbotsII\Robots\Veggies.  I do not have a Veggies subdirectory in my Robots directory as you apparently do, so I (correctly) get a common dialog popup asking me where the bleednrg bot file is.  I tell it, it loads it the bot file and the sim continues to run just fine.  No hang or crash.

I still suspect disk issues as the error you are getting is Path Not Found.  It may be you have problems with your DB install.  Are you running FAT or NTFS?  You might want to run chkdsk on yoru machine...

Try configuring a shorter repopulation cooldown period.  If you get the error sooner, then we will know it is occurring at veggie repopulation time.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 28, 2007, 12:23:18 PM
I am using XP so I am using NTFS. I hope there is nothing wrong with the harddisk, but to be sure, chkdsk is going to scan at next startup.
It hasn't got anything to do with the veggie-repop. It is even uccuring within a minute now, it happens even before 10000 cycles.

I am going to reinstall DB, there has probably happened something to the executable or in anything it uses, becouse you state there is nothing wrong with the sim and I get an error anyhow.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: EricL on November 28, 2007, 12:26:29 PM
I doubt it's the exe.  EXE's tend to either work or not.

It might be the autosave feature.  Again, a path / disk issue....

So I'm clear, when you set the cooldown interval to somethign short, like 1, does it change the timing on when you get the error or not?
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 28, 2007, 12:39:18 PM
Quote from: EricL
So I'm clear, when you set the cooldown interval to somethign short, like 1, does it change the timing on when you get the error or not?
NO, I am clear too, wasn't I earlier.
Changing doesn't affect anything about the time it gaves an error, the error is pretty much random, whatever you change. And isn't it like when you change veggie-repop-time it is not being set up before the next repop, is it. Atleast I don't see any veggies coming when I change the value to 1. And as I said the error occurs before 10000 cycles thus before veggie-repop.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 28, 2007, 12:55:47 PM
Just want to notice, the instalation of the original DB(2.0) fixed it, and it isn't giving the error anymore.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: EricL on November 28, 2007, 01:05:15 PM
The veggie repop counter is saved in the sim file, so it's not 10000 cycles from when you start the sim, it's 10000 cycles from the last repop.  You don't really know many cycles there are left to go after sim start before the 10000 countdown triggers the repopulation.  It may be happening 2 cycles after you start the sim.

Peter, I don't ask you to try things because I enjoy these lovely discussions.  I ask you because I have reasons based on an understanding of how the code actually works.  When you say something like "it hasn't got anything to do with veggy-repop" there is no way I can take that at face value.  You are not in the code.  There is no way you can know that.  I didn't ask you if it has anything to do with veggy repop - you arn't in a position to make that kind of assessment.  I asked you to try something very specific and tell me whether that changed things.  Sicne the problem is likely a function of your specific machine or your specific directory setup, only you can do these tests.  If it was something I could test on my machine, I wouldn't be bothering you.

You don't see veggies coming into the sim when you change the cooldown to 1?  I do.

Try changing the autosave interval.  Does that change the timing?



Quote from: Peter
Just want to notice, the instalation of the original DB(2.0) fixed it, and it isn't giving the error anymore.
Sounds like disk problems.....  Better run that chkdsk and free up some more space...
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 28, 2007, 01:42:33 PM
Quote
Peter, I don't ask you to try things because I enjoy these lovely discussions.  I ask you because I have reasons based on an understanding of how the code actually works.  When you say something like "it hasn't got anything to do with veggy-repop" there is no way I can take that at face value.  You are not in the code.  There is no way you can know that.  I didn't ask you if it has anything to do with veggy repop - you arn't in a position to make that kind of assessment.  I asked you to try something very specific and tell me whether that changed things.  Sicne the problem is likely a function of your specific machine or your specific directory setup, only you can do these tests.  If it was something I could test on my machine, I wouldn't be bothering you.
I said it hasn't got anything to do with veggie-repop becouse changing it didn't change anything, I would have said better that changing the veggie-repop didn't change the error-time, I laid there the conclusion it didn't had anything to do with it.
But, okay point made, I will try to not do it again.

And further as I don't know the code exactly, I don't know exactly what has to happen. And so what there has gone wrong and gone well, so what to tell, I thought there was nothing special, in fact the veggies not appearing was something strange, I didn't know it was strange. I could have said in the first place the error-time didn't change, you could probably have agreed with just that info, (I think).

And now it seems that as an user I am unreliable as error-signs giver, I can easily overlook something.(maybe this was something for remote assistance)

And now if I change the veggie repop to 1 I see veggies coming.

Quote
Quote
Just want to notice, the instalation of the original DB(2.0) fixed it, and it isn't giving the error anymore.
Sounds like disk problems.....  Better run that chkdsk and free up some more space...
I am going to run chkdsk at next startup, as in NTFS chkdsk can't run properly if already started.
I hope there is nothing wrong with it.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Numsgil on November 28, 2007, 03:12:30 PM
Peter, reinstalling the original 2.1 installation fixed it?  Visual Basic relies on its own run time libraries that have the damnable tendancy of running different on different people's machines.  Maybe it's different versions, I don't know.  But if reinstalling fixed the problem, I'd bet anything it was a problem with one of the VB run times.
Title: Errors when starting RESOLVED (NO REPRO)
Post by: Peter on November 29, 2007, 01:02:25 PM
Quote from: Numsgil
Peter, reinstalling the original 2.1 installation fixed it?  Visual Basic relies on its own run time libraries that have the damnable tendancy of running different on different people's machines.  Maybe it's different versions, I don't know.  But if reinstalling fixed the problem, I'd bet anything it was a problem with one of the VB run times.
Yes, correct, reinstalling the original 2.1 instalation fixed the problems. Using still desame 2.43t version.

Edit: and chkdsk said the harddisk was just fine, no single bad sector.