This has been occuring more and more frequently. 1,000 sector game. I'm not poolin CIM or ZTM data. I'm just using autopilot to warp through several econds and BAM a very annoying crash. I'm running 4.1.1 (regitered) on Windows XP Professional, 512 mb ram, ample hard drive space, AMD Athlon XP 1800 processor. Here's The error messages from XPs application log:
Faulting application attac.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.1.2600.1045, fault address 0x00002b59.
Faulting application attac.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.1.2600.1045, fault address 0x000237d0.
Faulting application attac.exe, version 0.0.0.0, faulting module attac.exe, version 0.0.0.0, fault address 0x00008b70.
============================================
I've noticed some other anomolies such as ATTAC being set by default for a 5000 sector game, and I am nto sure where to change this setting. Thsi seems to screw with the panel reporting how many holds I have on my ship, and what the holds are carrying.
In previous threads I've seen the authors reguest logs from the users. Are these logs that ATTAC keeps, I haven't been able to fidn them in the program directory. In any event, let me know, it's an annoying bug to have to work with
OK it seems autopilot ISN'T wast's causing the error. What's causing the error is porting and trading at any port. BOOM crash, page fault. Turning of the Helper Parses Data didn't solve this problem, I get similar crashes
Immediately upon logging on, I get erros as follows in the ATTAC console windw:
[ATTAC EROOR] Universe Size =0 Current Sector = 234 Where = status Threads =6
OK. i think i found the error. when parsing the warp path (occurs every time you move), i found a memory error. i was freeing invalid memory. I think that depending on your operating systme, it either crashed or didnt. I fixed this. Also, I found an error in the writeMemory routine which occurs if you see a planet greater than 40 characters. In this case, the DB gets corrupted and you crash, you next login then crashes since the DB is invalid.
I fixed the planet memory error and i now backup the attac DB file at every memory write. If I find an invalid file, then i restore from the backup.
I sent this fixed version to a user for testing.
if the fix is validated, the i will test it some more and release v4.1.2
earth.
I'm running Windows XP. the bug seems not to be from auto pilot but rather from porting. One thing I also noticed... I was testing this on a local server running tradewars. When I logged into that server I saw a session fo Tradewars that had crashed on my machine was still running on the server, even though ATTAC had long since crashed on my machine. When I quite the tradewars session from the server, I got another page fault from attac.exe, even though the application wasn't running, it must have been running in the background on my machine. As I've said I've narrowed the bug down, it only happens when I attemtp to trade at a port, and I think it has something to do with attac seeing the universe size as 0
can you replicate this??
You can send me email to continue this conversion.
The next time it crashes.. log back in, and do a holo-scan of the surronding sectors and email that to me.
earth.