This site makes extensive use of JavaScript.
Please enable JavaScript in your browser.
Live
PTR
10.2.7
PTR
10.2.6
Beta
Wowhead AddOns (Client/Looter) Issue? Report here!
Post Reply
Return to board index
Post by
Sas148
Ah BItDefender, always causing trouble... glad you were able to figure it out though, and it's something I can then suggest to others with similar trouble. Some users in the past had issues with SSL scanning from it, causing visitors to HTTPS pages to be unable to load them. Frequent attempts to reach BitDefender about it always resulted in no response.
Sorry for any inconvenience though. Only so much we can do about third party applications like this.
Post by
GraysonCarlyle
Wowhead client has always crashed occasionally for years now from a null pointer exception. I don't know if it crashes on WoW startup or closing, because it crashes silently. I figured it would be time to finally upload the crash logs. Each time it crashes, 3 windows events are created. Here are the latest ones:
Faulting application name: Wowhead_Client.exe, version: 1.9.1.1, time stamp: 0x59b1adf6
Faulting module name: Wowhead_Client.exe, version: 1.9.1.1, time stamp: 0x59b1adf6
Exception code: 0xc0000005
Fault offset: 0x00005797
Faulting process id: 0x24b4
Faulting application start time: 0x01d3c33123516b3b
Faulting application path: D:\World of Warcraft\Wowhead_Client.exe
Faulting module path: D:\World of Warcraft\Wowhead_Client.exe
Report Id: 0b9ddce7-a6ca-44dd-95cb-cfad762b145b
Faulting package full name:
Faulting package-relative application ID:
Fault bucket 109128318921, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Wowhead_Client.exe
P2: 1.9.1.1
P3: 59b1adf6
P4: Wowhead_Client.exe
P5: 1.9.1.1
P6: 59b1adf6
P7: c0000005
P8: 00005797
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER32CB.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3425.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3433.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3453.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Wowhead_Client.e_32895648c0a42cca85fc99828bb716b9df2538_8df61d5e_6a103a2e
Analysis symbol:
Rechecking for solution: 0
Report Id: 0b9ddce7-a6ca-44dd-95cb-cfad762b145b
Report Status: 268435456
Hashed bucket: 188eed6925d8638012e2b28f37c4335e
Faulting application name: Wowhead_Client.exe, version: 1.9.1.1, time stamp: 0x59b1adf6
Faulting module name: Wowhead_Client.exe, version: 1.9.1.1, time stamp: 0x59b1adf6
Exception code: 0xc000041d
Fault offset: 0x00005797
Faulting process id: 0x24b4
Faulting application start time: 0x01d3c33123516b3b
Faulting application path: D:\World of Warcraft\Wowhead_Client.exe
Faulting module path: D:\World of Warcraft\Wowhead_Client.exe
Report Id: a504e4aa-635a-413e-9e70-7d23c38dd596
Faulting package full name:
Faulting package-relative application ID:
And finally, the contents of the WER file:
Version=1
EventType=APPCRASH
EventTime=131666837733511820
ReportType=2
Consent=1
UploadTime=131666837738714517
ReportStatus=268435456
ReportIdentifier=735102b0-1265-4ec1-bb78-7a7c0de66a5d
IntegratorReportIdentifier=0b9ddce7-a6ca-44dd-95cb-cfad762b145b
Wow64Host=34404
Wow64Guest=332
NsAppName=Wowhead_Client.exe
AppSessionGuid=000024b4-0001-0006-3b6b-512331c3d301
TargetAppId=W:0006b59307d90083c46609821414fdcfbab800000900!0000e35779d1a250309d2f17a60875258ef9b87bbaca!Wowhead_Client.exe
TargetAppVer=2017//09//07:20:37:10!0!Wowhead_Client.exe
BootId=4294967295
ServiceSplit=2262383951
TargetAsId=15183
Response.BucketId=188eed6925d8638012e2b28f37c4335e
Response.BucketTable=1
Response.LegacyBucketId=109128318921
Response.type=4
Sig.Name=Application Name
Sig.Value=Wowhead_Client.exe
Sig.Name=Application Version
Sig.Value=1.9.1.1
Sig.Name=Application Timestamp
Sig.Value=59b1adf6
Sig.Name=Fault Module Name
Sig.Value=Wowhead_Client.exe
Sig.Name=Fault Module Version
Sig.Value=1.9.1.1
Sig.Name=Fault Module Timestamp
Sig.Value=59b1adf6
Sig.Name=Exception Code
Sig.Value=c0000005
Sig.Name=Exception Offset
Sig.Value=00005797
DynamicSig.Name=OS Version
DynamicSig.Value=10.0.16299.2.0.0.768.101
DynamicSig.Name=Locale ID
DynamicSig.Value=1033
DynamicSig.Name=Additional Information 1
DynamicSig.Value=1c01
DynamicSig.Name=Additional Information 2
DynamicSig.Value=1c01a0d5e13331384315d2ef20aa273d
DynamicSig.Name=Additional Information 3
DynamicSig.Value=f271
DynamicSig.Name=Additional Information 4
DynamicSig.Value=f271825e3b1839a45738f1558cdd483c
UI=D:\World of Warcraft\Wowhead_Client.exe
UI=The Wowhead Client installs and maintains an addon called the Wowhead Looter, which collects data as you play the game. It also has stopped working
UI=Windows can check online for a solution to the problem.
UI=Check online for a solution and close the program
UI=Check online for a solution later and close the program
UI=Close the program
LoadedModule=D:\World of Warcraft\Wowhead_Client.exe
LoadedModule=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule=C:\WINDOWS\System32\USER32.dll
LoadedModule=C:\WINDOWS\System32\win32u.dll
LoadedModule=C:\WINDOWS\System32\GDI32.dll
LoadedModule=C:\WINDOWS\System32\gdi32full.dll
LoadedModule=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule=C:\WINDOWS\System32\COMDLG32.dll
LoadedModule=C:\WINDOWS\System32\msvcrt.dll
LoadedModule=C:\WINDOWS\System32\combase.dll
LoadedModule=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule=C:\WINDOWS\System32\SspiCli.dll
LoadedModule=C:\WINDOWS\System32\CRYPTBASE.dll
LoadedModule=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule=C:\WINDOWS\System32\sechost.dll
LoadedModule=C:\WINDOWS\System32\shcore.dll
LoadedModule=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule=C:\WINDOWS\System32\SHELL32.dll
LoadedModule=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.16299.309_none_5d7d0b9ba7da9417\COMCTL32.dll
LoadedModule=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule=C:\WINDOWS\System32\windows.storage.dll
LoadedModule=C:\WINDOWS\System32\advapi32.dll
LoadedModule=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule=C:\WINDOWS\System32\powrprof.dll
LoadedModule=C:\WINDOWS\System32\pro!@#i.dll
LoadedModule=C:\WINDOWS\System32\ole32.dll
LoadedModule=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule=C:\WINDOWS\System32\WS2_32.dll
LoadedModule=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule=C:\WINDOWS\System32\IMM32.DLL
LoadedModule=C:\WINDOWS\system32\uxtheme.dll
LoadedModule=C:\WINDOWS\System32\MSCTF.dll
LoadedModule=C:\WINDOWS\system32\dwmapi.dll
LoadedModule=C:\WINDOWS\system32\napinsp.dll
LoadedModule=C:\WINDOWS\system32\pnrpnsp.dll
LoadedModule=C:\WINDOWS\system32\NLAapi.dll
LoadedModule=C:\WINDOWS\System32\mswsock.dll
LoadedModule=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule=C:\WINDOWS\System32\NSI.dll
LoadedModule=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule=C:\WINDOWS\System32\winrnr.dll
LoadedModule=C:\WINDOWS\System32\TextInputFramework.dll
LoadedModule=C:\WINDOWS\System32\CoreMessaging.dll
LoadedModule=C:\WINDOWS\System32\CoreUIComponents.dll
LoadedModule=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule=C:\Windows\System32\rasadhlp.dll
LoadedModule=C:\WINDOWS\System32\clbcatq.dll
LoadedModule=C:\WINDOWS\system32\wbem\wbemprox.dll
LoadedModule=C:\WINDOWS\SYSTEM32\wbemcomn.dll
LoadedModule=C:\WINDOWS\system32\wbem\wbemsvc.dll
LoadedModule=C:\WINDOWS\system32\wbem\fastprox.dll
State.Key=Transport.DoneStage1
State.Value=1
OsInfo.Key=vermaj
OsInfo.Value=10
OsInfo.Key=vermin
OsInfo.Value=0
OsInfo.Key=verbld
OsInfo.Value=16299
OsInfo.Key=ubr
OsInfo.Value=309
OsInfo.Key=versp
OsInfo.Value=0
OsInfo.Key=arch
OsInfo.Value=9
OsInfo.Key=lcid
OsInfo.Value=1033
OsInfo.Key=geoid
OsInfo.Value=244
OsInfo.Key=sku
OsInfo.Value=101
OsInfo.Key=domain
OsInfo.Value=0
OsInfo.Key=prodsuite
OsInfo.Value=768
OsInfo.Key=ntprodtype
OsInfo.Value=1
OsInfo.Key=platid
OsInfo.Value=10
OsInfo.Key=sr
OsInfo.Value=0
OsInfo.Key=tmsi
OsInfo.Value=115761
OsInfo.Key=osinsty
OsInfo.Value=3
OsInfo.Key=iever
OsInfo.Value=11.309.16299.0-11.0.56
OsInfo.Key=portos
OsInfo.Value=0
OsInfo.Key=ram
OsInfo.Value=32720
OsInfo.Key=svolsz
OsInfo.Value=94
OsInfo.Key=wimbt
OsInfo.Value=0
OsInfo.Key=blddt
OsInfo.Value=170928
OsInfo.Key=bldtm
OsInfo.Value=1534
OsInfo.Key=bldbrch
OsInfo.Value=rs3_release
OsInfo.Key=bldchk
OsInfo.Value=0
OsInfo.Key=wpvermaj
OsInfo.Value=0
OsInfo.Key=wpvermin
OsInfo.Value=0
OsInfo.Key=wpbuildmaj
OsInfo.Value=0
OsInfo.Key=wpbuildmin
OsInfo.Value=0
OsInfo.Key=osver
OsInfo.Value=10.0.16299.309.amd64fre.rs3_release.170928-1534
OsInfo.Key=buildflightid
OsInfo.Value=FE2BA97F-43C5-48BE-97E6-ACB9DE47C182.1
OsInfo.Key=edition
OsInfo.Value=Core
OsInfo.Key=ring
OsInfo.Key=containerid
OsInfo.Key=containertype
OsInfo.Key=edu
OsInfo.Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=The Wowhead Client installs and maintains an addon called the Wowhead Looter, which collects data as you play the game. It also
AppPath=D:\World of Warcraft\Wowhead_Client.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=B9625F41923F97AEFB16DEBD8E56E0DF
MetadataHash=422416402
Post by
mik3ron
so the past few days, I haven't been getting credit for uploading using the wowhead client. as far as I can tell, the upload was successful.
Post by
Sas148
so the past few days, I haven't been getting credit for uploading using the wowhead client. as far as I can tell, the upload was successful.
You can only receive reputation for Wowhead Client uploads twice per week, 25 each, up to 50 total.
See:
http://www.wowhead.com/reputation
Post by
termight
Found an issue wherein (only when playing my Warlock strangely enough), having the Wowhead Looter addon enabled would cause my Transmog screen to "reset" the page number to the page that contains the currently selected item. Making browsing through pages of Transmog options horribly frustrating.
I don't know exactly what's causing it, but using /etrace, searching of the text of all addons installed for those included TRANSMOG_COLLECTION_UPDATED hooks (the event that seemed to be triggering the "reset"), and disabling each of these addons one by one until the issue stopped; It happened to be the Wowhead Looter addon that was to blame as the issue goes away when disabled, then reoccurs when re-enabled.
Unrelated issue, I currently cannot run the Wowhead_Client.exe as it always fails on "Could not update a file. Please try again later." Which means I can't upload data either. :(
Post by
Sas148
Found an issue wherein (only when playing my Warlock strangely enough), having the Wowhead Looter addon enabled would cause my Transmog screen to "reset" the page number to the page that contains the currently selected item. Making browsing through pages of Transmog options horribly frustrating.
I don't know exactly what's causing it, but using /etrace, searching of the text of all addons installed for those included TRANSMOG_COLLECTION_UPDATED hooks (the event that seemed to be triggering the "reset"), and disabling each of these addons one by one until the issue stopped; It happened to be the Wowhead Looter addon that was to blame as the issue goes away when disabled, then reoccurs when re-enabled.
Unrelated issue, I currently cannot run the Wowhead_Client.exe as it always fails on "Could not update a file. Please try again later." Which means I can't upload data either. :(
Re: transmog screen - it's something we haven't been able to figure out in the past, unfortunately, I can't even replicate it myself.
Re: "could not update a file" -- I replied to another thread you bumped with a solution: remove the Beta path in the client options, it's trying to put the looter in your alpha client but can't because Blizzard isn't yet allowing addons.
Post by
KazlaWr
Hey!
Thanks for you amazing job!
I've an issue with too large upload, so I clear the Variables and the upload works fine.
I keep the previous variables and I would like to know if it is possible to split it into small parts to give to the community all my stats (around 71k kills counts this month).
Thanks you in advance,
SD
Post by
Sas148
Unfortunately there's no way to submit data outside of the client. We appreciate the attempt though! All I can suggest is trying to upload more frequently if you're encountering this problem often.
Post by
mik3ron
Oh ok, Thank you!
Post by
Rillarri
I also run Bitdefender and after seeing the previous post i too disabled my protection and the upload finished successfully. I went into BitDefender and put the wowhead client executable and the addons folder in as exclusions in the hope that i don't have to constantly disable BD every time i want to upload.
Post by
Lazare69
I installed Wowhead Client years ago and today updated it to 1.2.2 on my MacPro.
When it first opens and I flip the "arrow" down so that I can see what is going on I get:
2018.05.02 01:17:27 am: Authentication failed.
2018.05.02 01:17:27 am: Checking for Wowhead Looter addon updates…
2018.05.02 01:17:27 am: Looks like you're up-to-date!
2018.05.02 01:18:24 am: Authentication failed.
2018.05.02 01:19:50 am: Authentication failed.
2018.05.02 01:20:13 am: Authentication failed.
The above is multiple attempts to get it running. One thing I have noticed also is that I do not have the buttons shown on the Mac section of the
Wowhead Client
page
I have triple checked that my Wowhead username and password were correct (by logging in and out of Wowhead.com successfully) yet I get "Authentication failed" each time that I open the application.
Might I get a little help from Wowhead on this?
Thanks in Advance and Cheers!
Lazare69
Post by
cxarli
With the latest update to Mac OS High Sierra, the system is warning that 32-bit applications will soon be unsupported in Mac OS. This warning displayed when I started Wowhead Client tonight. Will there be a 64-bit update for Mac before the next version of Mac OS comes out?
Post by
Tequima
I see on
another thread
that Wowhead doesn't yet work with BfA Beta. (I'm getting Beta World of Warcraft path is invalid when I try to point it at F:\WoW\World of Warcraft Beta\WowB.exe).
Where do I need to look to see when it's fixed, here or on Discord?
Post by
Sas148
Might I get a little help from Wowhead on this?
Thanks in Advance and Cheers!
Lazare69
Contact me via so I can look into manually resetting your account password, if the client thinks your username/password is wrong then there's likely a reason for that (you're using your username, not email, in the client right?).
With the latest update to Mac OS High Sierra, the system is warning that 32-bit applications will soon be unsupported in Mac OS. This warning displayed when I started Wowhead Client tonight. Will there be a 64-bit update for Mac before the next version of Mac OS comes out?
We're working to make a new client, which I'm confident will be 64-bit so it should be okay by the time 32-bit is unsupported; hopefully.
I see on
another thread
that Wowhead doesn't yet work with BfA Beta. (I'm getting Beta World of Warcraft path is invalid when I try to point it at F:\WoW\World of Warcraft Beta\WowB.exe).
Where do I need to look to see when it's fixed, here or on Discord?
You can check the 'Known Issues' portion of this original post to see the status. Once it's fixed I'll mark it as 'Fixed'.
Post by
Sas148
The Wowhead Client will now properly work with BFA Beta. Please run the client to recieve the latest update.
Post by
digital81
Any word on fixing the issue with Looter where when at the Transmog Vendor it keeps refreshing the page back to the page your currently used transmog is on? For example, if I am on Weapon Transmogs and I am using an appearance from page two and try to switch to any other page of appearances it just keeps automatically putting me back on page two so I can't look-at or choose Transmogs from any other page besides page two. I've reproduced this with and without other addons enabled and the problem goes away once Looter is disabled.
Post by
Drexxis
Some new LUA errors following
Beta Build 26629
. These results were recorded just before this post.
1/4
Message: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4971: attempt to call global 'CalendarGetDate' (a nil value)
Time: Wed May 16 19:37:14 2018
Count: 1
Stack: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4971: attempt to call global 'CalendarGetDate' (a nil value)
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4971: in function `wlGetDate'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4980: in function `wlGetTime'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:779: in function `?'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4335: in function <Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4333>
Locals: (*temporary) = <function> defined =:-1
(*temporary) = 2
(*temporary) = nil
(*temporary) = "attempt to call global 'CalendarGetDate' (a nil value)"
select = <function> defined =:-1
2/4
Message: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4971: attempt to call global 'CalendarGetDate' (a nil value)
Time: Wed May 16 19:37:15 2018
Count: 1
Stack: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4971: attempt to call global 'CalendarGetDate' (a nil value)
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4971: in function `wlGetDate'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4980: in function `wlGetTime'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:3038: in function `?'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4335: in function <Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4333>
Locals: (*temporary) = <function> defined =:-1
(*temporary) = 2
(*temporary) = nil
(*temporary) = "attempt to call global 'CalendarGetDate' (a nil value)"
select = <function> defined =:-1
3/4
Message: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4971: attempt to call global 'CalendarGetDate' (a nil value)
Time: Wed May 16 19:37:15 2018
Count: 1
Stack: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4971: attempt to call global 'CalendarGetDate' (a nil value)
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4971: in function `wlGetDate'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:689: in function `?'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4335: in function <Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4333>
Locals: (*temporary) = <function> defined =:-1
(*temporary) = 2
(*temporary) = nil
(*temporary) = "attempt to call global 'CalendarGetDate' (a nil value)"
select = <function> defined =:-1
4/4
Message: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4971: attempt to call global 'CalendarGetDate' (a nil value)
Time: Wed May 16 19:39:16 2018
Count: 4289
Stack: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4971: attempt to call global 'CalendarGetDate' (a nil value)
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4971: in function `wlGetDate'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4980: in function `wlGetTime'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4349: in function <Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4344>
Locals: (*temporary) = <function> defined =:-1
(*temporary) = 2
(*temporary) = nil
(*temporary) = "attempt to call global 'CalendarGetDate' (a nil value)"
select = <function> defined =:-1
The last one is relentlessly counting up.
Post by
Sas148
The LUA errors will be fixed soon. Unfortunately this is likely to happen with each new build.
As far as the Looter causing the transmog menu to change pages, we still haven't been able to replicate it ourselves, but we're looking to replace the client in the near future so hopefully that may resolve the problem.
Post by
Voxxel
The 4/4 is an endlessly counting lua bug and it forces to pop the "disable addon recommendation blizzard popup" on every minute or so, even with lua errors disabled.
Post by
Tequima
Getting the same error this morning.
Post Reply
You are not logged in. Please
log in
to post a reply or
register
if you don't already have an account.