APB Ultimate

[RottenMind]

Thx man

and Rotten thx for script auto it too, but i haven't test because my wife was run over by a car. so i test next week when she come back.

Huh, world is nasty place if you try live in "Glass Cube" then some one try poisoning your oxygen supply... if live normal life, then you get over run by careless driver, I wish she recover fast.

... life still goes on.

I started moving to APBU and it also means few new scripts when ready I post Dropbox links.

First script will clean APBx -folders, keeps settings/profiles and do filecopy in order update both Bots. It is not Autoupdate, but it will help to keep multiple Bot instances files updated or clean_sweep after fatal failures.

Second one Start both Bots and try keep them running even if internal relog or other safeguard fails. It cant detect if Bot is stuck or not, it just use brute force to keep it running, but works perfectly if U are on holidays or your remote PC do many restarts.

...so I dont have wait program perfection or hire "friendly Indian" when I can use stupid script. Both script and Bot may fail but at end you have bigger chances get 90% online time, when script does it job multiple times per day (set time yourself 1 - xxx min.).

I will also include some fancy pictures and anyway all support for those creations will be found behind link what I post later.

Scripts will be done with Autoit, but are really easy to move in AHK or other program environment, because most needed "variables" are allready know. I just lack C++ experience and found Autoit really easy to use and understand.

ps. If you Beta -testing its not good use script, timeouts and errors just disappears when process is restarted, .

[Darxide23]

Alright, APBU ran overnight without any problems and when I left for class this morning and it was still running fine. When I got home I had another "Out of Memory" error but this time I managed to open my process viewer to see that APBU was using 3.5GB or RAM. I couldn't save the screenshot before everything froze up and I had to reboot. I didn't see the log before it went down.

I also saw that I had run out of a resource. I wonder if the retry loop is where the memory leak is.

[Methuselas]

Just curious, but what jobs are you running? I only ask cos I have 4 instances of the bot running on a single machine, doing leadership jobs, plus gathering jobs. I haven't seen any sort of leaks, but getting more timeouts on my 6 toon account. It always relogs just fine, but maybe I need to start checking. Granted, this box is dedicated to running bots.

[Rhendanwan]

I have also encountered a nasty memory leak. twice so far. after about 5-6h of working. I was doing only leadership tasks. version 0.3.6b.
it took the whole RAM. couldn't do anything but restart the computer. I couldn't see the log window cause it was unresponsive so can't give any more info..

will leave the log window open from now on to see if anything is on it if it happens again...

[Darxide23]

Just curious, but what jobs are you running? I only ask cos I have 4 instances of the bot running on a single machine, doing leadership jobs, plus gathering jobs. I haven't seen any sort of leaks, but getting more timeouts on my 6 toon account. It always relogs just fine, but maybe I need to start checking. Granted, this box is dedicated to running bots.

It doesn't seem to matter what jobs. I've changed my queue a few times last night so last night's out of memory and today's out of memory had completely different queues.

[Methuselas]

It doesn't seem to matter what jobs. I've changed my queue a few times last night so last night's out of memory and today's out of memory had completely different queues.

This is interesting..... I checked all my bots and they're all running in the 90mb-128mb range.....

[daihatsou]

How do i put refine astral diamonds? I dont see any option for that?

[BaseN]

Guys I told you already that there is no leak. A memory leak happens when you allocate memory on the heap and then you don't deallocate it. This happens nowhere in the APBU's code.

What happens in this case is this: http://www.ownedcore.com/forums/mmo/...ml#post2983385 (APB Ultimate)

There is a situation where the bot can get abnormally stuck in a particular loop that allocates memory on the heap. This was triggered when you hit the X button to close the window without hitting stop first and I fixed it by hooking at the close event and calling the stop button function prior to actually closing.

What happens in this case is that somehow this gets triggered for you due to a timeout happening at some specific point in time. I thought the changes in 0.3.9 could have caused it but apparently that is not the case since Rhendanwan says it happened on 0.3.6 as well (which reminds that you should report it when something like this happens because I've spent 2 days looking for this obviously in the wrong place). I have 3 instances running since the last gateway maintenance hoping that I could reproduce this but they are running perfectly fine since then.. so only option now is to implement log to file so I can see log of when it happens because I can't see what triggers it if I can't reproduce it.

@daihatsou: Read first post maybe?

[Darxide23]

Got it this time before the computer crashed with it:

https://i.imgur.com/RdcBsmo.png

Also, this is the full error that it gave:

Problem signature:
Problem Event Name: APPCRASH
Application Name: APBUltimate.exe
Application Version: 0.0.0.0
Application Timestamp: 530e9076
Fault Module Name: Qt5WebKit.dll
Fault Module Version: 5.2.2.0
Fault Module Timestamp: 53041771
Exception Code: c0000005
Exception Offset: 0000000000210ec5
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 42f3
Additional Information 2: 42f3b781db1ae0b8435b0bebe3ff271e
Additional Information 3: 8258
Additional Information 4: 8258737b6d5e810759b068a465128efe

[packetlossb]

I'm still having an issue with autologin with 3.9. I had increased the internal loop timeout to 10, but it seems the issue is it never tried to autolog back in after encountering the timout while switching characters. This only happened on 1 out of 5 that were running and when I hit the login button in the morning it did log back in. Yes, autologin is checked.

Update. I did happen to see it time out while starting a new task and it DID auto log into the gateway after that timeout so this issue I noticed seems specific to timing out when switching characters.


20:54:47: Slot 4 is Running.
20:54:47: Delaying for 255 seconds.
20:59:03: Restarting loop.
20:59:04: Switching to character SlotA
21:04:20: Switching Character timed out. Retry 1...
21:04:49: Switching Character timed out. Retry 2...
21:04:50: Switching Character timed out. Retry 3...
21:04:51: Switching Character timed out. Retry 4...
21:04:52: Switching Character timed out. Retry 5...
21:04:53: Switching Character timed out. Retry 6...
21:04:54: Switching Character timed out. Retry 7...
21:04:55: Switching Character timed out. Retry 8...
21:04:56: Switching Character timed out. Retry 9...
21:04:56: Maximum timeout reached. Stopping
21:04:57: Stopping. Please Wait!
21:04:57: Stopped! Timeout while switching character.

[Rhendanwan]

I have encountered another issue.. I got some kind of a "network connection issue" line in the log,so it got disconnected from gateway and next line said it will relog after 60sec but nothing happened for about 3h.
when I got there the bot was unresponsive and couldn't press stop or start button so had to close it in task manager. internet connection works as far as I can see.

so if by some chance router got restarted or if it was a power failure is it possible that the bot wouldn't continue working after the connection was established again?

[RottenMind]

While BaseN "wrestling" with True programs I did two scripts to helps myself and hopefully some others to keep BOTH APBx Bots running, updated and clean up Bot directories as well... with one click (after you Setup things properly)

Download all stuff from here. Use virus scanner, check .au3, .txt files and let it grind.

ZIP -file contains all, but APBx program files. Unzipping it makes things easier.

APBI use "Button names" for mouse clicks, reliable way to click object.

APBU use "imagesearch" or "relative windows coordinates" -mode, both are unreliable way to click objects, but it works for me.(it try both way locate and click "Start" button if fails then it fails)


For BaseN, when you got time for it...

Commandlines, StartBot, StopBot, ExitBot and Delay in seconds, but those options are just "Tip of Iceberg" and with script it can be done, .


ps. If you extend Bot ability accept profile rotation and scripts... huh, then this Bot will became more interesting than NW itself.

[BaseN]

Got it this time before the computer crashed with it:
Also, this is the full error that it gave:

See if there is a crash dump generated in C:\Users\your_username\AppData\Local\Microsoft\Windows\WER\ReportQueue

I'm still having an issue with autologin with 3.9. I had increased the internal loop timeout to 10, but it seems the issue is it never tried to autolog back in after encountering the timout while switching characters. This only happened on 1 out of 5 that were running and when I hit the login button in the morning it did log back in. Yes, autologin is checked.

Update. I did happen to see it time out while starting a new task and it DID auto log into the gateway after that timeout so this issue I noticed seems specific to timing out when switching characters.


20:54:47: Slot 4 is Running.
20:54:47: Delaying for 255 seconds.
20:59:03: Restarting loop.
20:59:04: Switching to character SlotA
21:04:20: Switching Character timed out. Retry 1...
21:04:49: Switching Character timed out. Retry 2...
21:04:50: Switching Character timed out. Retry 3...
21:04:51: Switching Character timed out. Retry 4...
21:04:52: Switching Character timed out. Retry 5...
21:04:53: Switching Character timed out. Retry 6...
21:04:54: Switching Character timed out. Retry 7...
21:04:55: Switching Character timed out. Retry 8...
21:04:56: Switching Character timed out. Retry 9...
21:04:56: Maximum timeout reached. Stopping
21:04:57: Stopping. Please Wait!
21:04:57: Stopped! Timeout while switching character.

Will look into it.

I have encountered another issue.. I got some kind of a "network connection issue" line in the log,so it got disconnected from gateway and next line said it will relog after 60sec but nothing happened for about 3h.
when I got there the bot was unresponsive and couldn't press stop or start button so had to close it in task manager. internet connection works as far as I can see.

so if by some chance router got restarted or if it was a power failure is it possible that the bot wouldn't continue working after the connection was established again?

That line in the log is part of the new network drop detection code. It means the url requested by APBU never completed with success or fail status so there's no network connectivity to the gateway server at all. It is supposed to relog if relog and autologin is enabled. It will keep retrying until network is restored so it can continue. But maybe something is not working right so I will check it out. Can you please post me the log from when this happened?

For BaseN, when you got time for it...

Commandlines, StartBot, StopBot, ExitBot and Delay in seconds, but those options are just "Tip of Iceberg" and with script it can be done, .

This is not possible unless I make a launcher process that runs and controls the actual APBU process via command line switches like this. I'll keep it in mind for when everything else is done.

Edit: Actually if I make such a launcher I'll go one step beyond and make it control several instances of APBU/multiple accounts.

ps. If you extend Bot ability accept profile rotation and scripts... huh, then this Bot will became more interesting than NW itself.

This is already in the TODO list

[Darxide23]

See if there is a crash dump generated in C:\Users\your_username\AppData\Local\Microsoft\Windows\WER\ReportQueue

There were none in ReportQueue for APBU but there was one in ReportArchive.

Only file in the folder was report.wer and here it is:

Version=1
EventType=APPCRASH
EventTime=130382149769353265
ReportType=2
Consent=1
ReportIdentifier=1790ca0f-a1d3-11e3-87ca-94de80aef5d6
IntegratorReportIdentifier=1790ca0e-a1d3-11e3-87ca-94de80aef5d6
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=APBUltimate.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=530e9076
Sig[3].Name=Fault Module Name
Sig[3].Value=Qt5WebKit.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=5.2.2.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=53041771
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000210ec5
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=42f3
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=42f3b781db1ae0b8435b0bebe3ff271e
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=8258
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=8258737b6d5e810759b068a465128efe
UI[2]=D:\Users\***\Desktop\APBUltimate\APBUltimate.exe
UI[3]=APBUltimate.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=D:\Users\***\Desktop\APBUltimate\APBUltimate.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=D:\Users\***\Desktop\APBUltimate\Qt5Core.dll
LoadedModule[5]=C:\Windows\system32\USER32.dll
LoadedModule[6]=C:\Windows\system32\GDI32.dll
LoadedModule[7]=C:\Windows\system32\LPK.dll
LoadedModule[8]=C:\Windows\system32\USP10.dll
LoadedModule[9]=C:\Windows\system32\msvcrt.dll
LoadedModule[10]=C:\Windows\system32\ole32.dll
LoadedModule[11]=C:\Windows\system32\RPCRT4.dll
LoadedModule[12]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[13]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[14]=C:\Windows\system32\WS2_32.dll
LoadedModule[15]=C:\Windows\system32\NSI.dll
LoadedModule[16]=D:\Users\***\Desktop\APBUltimate\icuin52.dll
LoadedModule[17]=D:\Users\***\Desktop\APBUltimate\icuuc52.dll
LoadedModule[18]=D:\Users\***\Desktop\APBUltimate\icudt52.dll
LoadedModule[19]=D:\Users\***\Desktop\APBUltimate\MSVCR110.dll
LoadedModule[20]=D:\Users\***\Desktop\APBUltimate\MSVCP110.dll
LoadedModule[21]=D:\Users\***\Desktop\APBUltimate\Qt5Gui.dll
LoadedModule[22]=C:\Windows\system32\OPENGL32.dll
LoadedModule[23]=C:\Windows\system32\GLU32.dll
LoadedModule[24]=C:\Windows\system32\DDRAW.dll
LoadedModule[25]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[26]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[27]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[28]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[29]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[30]=C:\Windows\system32\dwmapi.dll
LoadedModule[31]=D:\Users\***\Desktop\APBUltimate\Qt5Network.dll
LoadedModule[32]=C:\Windows\system32\DNSAPI.dll
LoadedModule[33]=C:\Windows\system32\CRYPT32.dll
LoadedModule[34]=C:\Windows\system32\MSASN1.dll
LoadedModule[35]=D:\Users\***\Desktop\APBUltimate\Qt5WebKit.dll
LoadedModule[36]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[37]=C:\Windows\system32\VERSION.dll
LoadedModule[38]=C:\Windows\system32\WINMM.dll
LoadedModule[39]=D:\Users\***\Desktop\APBUltimate\Qt5Widgets.dll
LoadedModule[40]=C:\Windows\system32\SHELL32.dll
LoadedModule[41]=D:\Users\***\Desktop\APBUltimate\Qt5WebKitWidgets.dll
LoadedModule[42]=D:\Users\***\Desktop\APBUltimate\Qt5OpenGL.dll
LoadedModule[43]=D:\Users\***\Desktop\APBUltimate\Qt5PrintSupport.dll
LoadedModule[44]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[45]=C:\Windows\system32\COMDLG32.dll
LoadedModule[46]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_a4d3b9377117c3df\COMCTL32.dll
LoadedModule[47]=C:\Windows\system32\IMM32.DLL
LoadedModule[48]=C:\Windows\system32\MSCTF.dll
LoadedModule[49]=C:\Windows\system32\cryptbase.dll
LoadedModule[50]=D:\Users\***\Desktop\APBUltimate\platforms\qwindows.dll
LoadedModule[51]=C:\Windows\system32\uxtheme.dll
LoadedModule[52]=D:\Users\***\Desktop\APBUltimate\imageformats\qico.dll
LoadedModule[53]=D:\Users\***\Desktop\APBUltimate\imageformats\qjpeg.dll
LoadedModule[54]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[55]=C:\Windows\system32\rsaenh.dll
LoadedModule[56]=D:\Users\***\Desktop\APBUltimate\ssleay32.dll
LoadedModule[57]=D:\Users\***\Desktop\APBUltimate\LIBEAY32.dll
LoadedModule[58]=C:\Windows\system32\mswsock.dll
LoadedModule[59]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[60]=C:\Windows\system32\WINNSI.DLL
LoadedModule[61]=C:\Windows\system32\rasadhlp.dll
LoadedModule[62]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[63]=C:\Windows\system32\profapi.dll
LoadedModule[64]=C:\Windows\System32\wshtcpip.dll
LoadedModule[65]=C:\Windows\System32\wship6.dll
LoadedModule[66]=C:\Windows\System32\fwpuclnt.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=APBUltimate.exe
AppPath=D:\Users\***\Desktop\APBUltimate\APBUltimate.exe

[Rhendanwan]

That line in the log is part of the new network drop detection code. It means the url requested by APBU never completed with success or fail status so there's no network connectivity to the gateway server at all. It is supposed to relog if relog and autologin is enabled. It will keep retrying until network is restored so it can continue. But maybe something is not working right so I will check it out. Can you please post me the log from when this happened?

I did not save it :/
sorry it was a mistake not to copy the full text here.. I closed the bot too soon from task manager :/
is the log saved somewhere?