Honorbuddy v2.5.11769.750

Hi, Fgame, and thanks for the logs.

Neither one of these logs illustrates Gatherbuddy doing a "Hearth and Exit" due to full bags.

One log is just truncated, and the other log shows Honorbuddy is shut down because the WoWclient exited.

Since neither one of these logs illustrates a problem, there is no bug for us to capture.

cheers,
chinajade


[size=-2]Ref: Fgame's original post w/log[/size]

 

Hi, Scenix, and thanks for the log.

Please do a "clean install", and install no third-party products.

Honorbuddy:HelpDesk:"Clean installing" Honorbuddy​

In particular, it looks like your Combat Routine is not ready for the pre-WoD Honorbuddy. Do not install any third-party product until the author explicitly states it is ready for pre-WoD Honorbuddy.

cheers,
chinajade

[size=-2]Ref: Scenix's original post w/log[/size]

 

Hi, Flyg, and thanks for the kernel error details!

We've added your data point to HB-1306 ("Reports of HB causing WoWclient crash and BSoD").

However, in your case, its the WoWclient causing the crash. Try switching the WoWclient to DX9 mode, and see if the problem persists.

cheers,
chinajade


[size=-2]Ref: Flyg's original post w/log[/size]

 

Hi, DraGoNo, and thanks for the log.

[22:30:49.449 Q] Bot stopping! Reason: Nothing more to do.​

It looks like your profile executed as it was supposed to, and "got done". If you do not believe this is correct, please contact the profile's author and allow him to report the specifics of the problem he observes.

cheers,
chinajade


[size=-2]Ref: DraGoNo's original post w/log[/size]

 

Hi, all,

First, let's reboot the machine.

Second, let's clearing the caches:

HelpDesk: Cache corruption problems​

If no joy, let's try switching the WoWclient to DX9, then relaunch the WoWclient before launching Honorbuddy.

cheers,
chinajade


[size=-2]Ref: Cataphract's original post w/log[/size]
[size=-2]Ref: WTB A Noob's original post w/log[/size]

 

Hi, RyanD,

As stated in the '.750 Known Bugs List, we are not collecting reports against Singular. We just need to give Bobby53 time to catch up. All Combat Routine authors have been hit really, really hard by the pre-WoD changes.

cheers,
chinajade


[size=-2]Ref: RyanD's original post w/log[/size]

 

Hi, Melcekial, and thanks for this info!

We've added this data point to HB-1306 ("Reports of HB causing WoWclient crash and BSoD "). But to chase problems like this, we really need the WoWclient crash report (its a .txt file in the WoW directory).

If the problem happen again for you, please include the WoWclient crash report in addition to the screenie and log you've already shown us.

thanks!
chinajade


[size=-2]Ref: Melcekial's problem report w/log[/size]

 

Hi, Altec, and thanks for all those details.

We've opened HB-1338("HB API reporting inappropriate LocalPlayer.CurrentRage values") against the issue.

cheers,
chinajade


[size=-2]Ref: Altec's problem report w/log[/size]

 

Hi again, Melcekial,

Perfect! Thanks so much, and they've been added to HB-1306.

cheers,
chinajade


[size=-2]Ref: Melcekial's WoWclient crash logs[/size]

 

Hi, Cataphract,

Thanks for trying all that. I'm at a loss on this one other than to say something is seriously not right with your machine/installation.

[06:23:54.390 N] (Singular) -22.7 days since Windows was restarted​

k, this is a time in the future. Very bad.

[Ref: "UnknownProfile" @line 59]​

We've no clue what profile we're running.

At this point, all I've got for you is to suggest a "clean install":

Honorbuddy:HelpDesk:"Clean installing" Honorbuddy​

cheers,
chinajade


[size=-2]Ref: Cataphract's original post w/log[/size]

 

Hi, Melcekial,

Just a follow-up with info from MaiN...

HB-1306 has been closed as "Won't fix" with the following message:

"The WoW crash log contains no traces of anything Honorbuddy would touch, but it contains a DLL that I have seen on previous reports of crashes (4-5 reports in 5 months): rlls.dll. This is some spyware:
http://deletemalware.blogspot.dk/2011/04/remove-relevant-knowledge-uninstall.html"​

After explicitly addressing the "Relevant Knowledge" spyware, you may also want to run a Spyware-detection tool, like:

Spybot - Search & Destroy (we are not endorsing this product)
or another one​

cheers,
chinajade

 

Hi, All,

We've opened HB-1342 to monitor this situation. Whenever the WoWclient crashes, we'll need you to also attach the WoWclient crash log (a .txt file in the WoW directory).

You should also thoroughly check your computer for Spyware.

cheers,
chinajade


[size=-2]Ref: FadetoGrey's original post w/log[/size]
[size=-2]Ref: Cataphract's original post w/log[/size]

 

Hi, DevAnse,

Indeed, the profile was what was in error. The <Min*> tags have never been supported inside a GrindArea.

cheers,
chinajade


[size=-2]Ref: DevAnse's original post w/log[/size]

 

Hi, Ksmaze,

We're discarding this issue, since the log is not from this release.

cheers,
chinajade


[size=-2]Ref: Ksmaze's original post w/non-release log[/size]

 

Hi again, Unk2, and thank you for the log.

Even with a log, "Bot broken" is not enough information with which to write up a report. What are your observations? Was the toon moving to the hotspots where the quest mobs were located on the map? Were there any mobs at those locations?

cheers,
chinajade


[size=-2]Ref: Unk2's log[/size]

 

Hi, Ksmaze, and thank you for log.

We've opened HB-1346 ("ArcheologyBuddy failing for Druid") against this issue.

cheers,
chinajade


[size=-2]Ref: Ksmaze's problem report w/log[/size]

 

Hi, Sea, and thank you for the log.

This log makes absolutely no sense. It looks like there are Navigational/Mesh errors being encountered before the profile starts executing. I can't imagine why that would happen unless Honorbuddy was trying to go reclaim your corpse.

You might try clearing your caches.

HelpDesk: Cache corruption problems​

This doesn't appear to be a bug with Honorbuddy, but something awry with your installation.

cheers,
chinajade

[size=-2]Ref: Sea's original post w/log[/size]

 

Hi, TreeK, and thanks for the log.

We've opened HB-1347 ("ProfessionBuddy not switching characters successfully") against this issue.

cheers,
chinajade


[size=-2]Ref: TreeK's problem report w/log[/size]

 

Hi, Fgame, and thank you for the log.

Once again, these logs DO NOT show Gatherbuddy2 "Hearthing and Exiting".

Perhaps it is one of your plugins that have been mis-configured:

[13:12:28.724 D] theTramper gather
[13:12:28.724 D] rndbuddy ​

Please do a "clean install" as described in the article below. Add NO third-party products. Repeat the problem using JUST the "clean install"—no third-party anything. Then show us the log of the problem from the "clean install".

Honorbuddy:HelpDesk:"Clean installing" Honorbuddy​

cheers,
chinajade


[size=-2]Ref: Fgame's original post w/log[/size]

 

Hi, Flyg,

Try doing a "clean install"—no third-party products—and repeat the problem. If the problem does not manifest, its a third-party product interaction.

MaiN has also suggested Spyware can cause WoWclient crashes (and has captured several internal examples to prove it). You should also run a Spyware detection and removal tool.

And one last thing, I've personally had problems with BitDefender in 'aggressive' settings monitoring wireless connections. It could be your AV interfering, and you may want to look into that also.

At this time, we do not believe this to be an Honorbuddy bug, but interference from an external program. See HB-1306 in the '.750 Known Bugs List.

cheers,
chinajade

[size=-2]Ref: Flyg's original post w/log[/size]