Code center > Bug reports
league out of memory error
Jez:
I reran the F1 league for 2 1/2 days before it crashed, then I realised I hadn't updated DB from .9o.
Downloaded DB .9r...
This time it all seemed to run a bit faster and after only ~6hrs, match 12, DIN2 v Kyushu I got an error, out of memory message. (run-time error 7, out of memory then appeared when I closed first error message)(then I got a send this to MS? error message after closing second message)
Round 1 of 5
DIN2 0 - 11
Kyushu 0 - 7
Error.sim attached in case it provides any clues. I'll rerun the league tonight to see if it happens again.
EricL:
yea, I've been chasing this one for a while now. I've got a slow memory leak somewhere. I don't think it is specific to leagues. It takes days to hit when running in the debugger, which I am doing now. Hopefully, I can get it to crash this weekend...
Jez:
Good to know you have a handle on this problem already.
Took 9 bot entries this time btw, interupted S. Conquistador's climb to the top. I'll do it one more time, in case it is something that leaks more when rerunning the leagues and you have trouble tracing it. I figure if I can get the problem three times in less than six hours each time then an F1 league rerun might be a quicker way to find.
I'm sure I have asked and had an answer to this before but is there a way I can run this debugger as well and provide you with more specific fault finding info than I am atm? Seems a shame to leave you spending days to find the info needed to fix faults if there is a way to (even partially) share out the workload in some way.
EricL:
--- Quote from: Jez ---I'm sure I have asked and had an answer to this before but is there a way I can run this debugger as well and provide you with more specific fault finding info than I am atm? Seems a shame to leave you spending days to find the info needed to fix faults if there is a way to (even partially) share out the workload in some way.
--- End quote ---
Sure, if you like. All you really need to do is download the source code and install a copy of VB6. VB6 is an IDE - an Integrated Development Evironment, the precursor to today's Visual Studio - that means it includes an editor, debugger, compiler, etc. all in one. So when I say I'm running DB "in the debugger" or "in the IDE" what I mean is that I'm running the program "inside" Visual Basic using the VB interpreter to interpret the basic source code in real time instead of instead of running the compiled executable like most people do. This real-time source code interpretation is one reason running "in the IDE" is perhaps 10X slower than running the compiled code and why it can take so damn long to find certain kinds of problems.
All you need to do is use VB to open and load up the DB VB project file (called Iersera.vbp) and hit the play button (or F5) in VB6. This will start DB like normal, just running "within" VB6. Now when there's a crash, VB will catch it (usally) and tell you on what source code line the problem is occurring (though often the actual root cause of the problem lies somewhere else and takes soem analysis to determine just why the code is doing what it is doing.)
There are a few additional things to be aware of. In particular, there are a few places where exception handling logic in the source code should be disabled when running in VB so as to let VB handle the problems instead of the code itself. Makes for cleaner debugging. Then there are the many tips and tricks to debugging - breakpoints, watch expressions, etc. - but just getting VB6 installed and the source code running is the big hurdle and the first main step. Let me know if/when you want more info on the rest of the details. Cheers.
Jez:
Where do I find the latest source code pls, only seem to be able to find it for C++
Navigation
[0] Message Index
[#] Next page
Go to full version