Two issues with WoWheadlooter on current beta 7.0.3

Post by liquidbasex

The first issue appears on login to charscreen or the world. Client crashes with a crit error which is releated to wowheadlooter.

Error:
==============================================================================
World of WarCraft: Beta Build (build 21691)

Exe: D:\World of Warcraft Beta\WowB-64.exe
Command: "D:\World of Warcraft Beta\WowB-64.exe" -launcherlogin -noautolaunch64bit -launch -uid wow_beta
Time: May 14, 2016 4:33:31.367 PM
User: user
Computer: computer
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program: D:\World of Warcraft Beta\WowB-64.exe
ProcessID: 1080
Exception: ACCESS_VIOLATION

The instruction at "0x00007ff6f7e6e286" referenced memory at "0x0000000000000050".
The memory could not be "read".

<Version> 7.0.3.21691
<Config> Beta
<Inspector.ProjectId> 10
<Inspector.BuildNumber> 21691
<Inspector.Branch> 7.0.3
<Application> World of WarCraft
<ApplicationType> Client
Type: WoWB
Executable UUID: 86AA9C0E-F200-43A5-A39B-6924B25C95DA
<Wow.Platform> X64
<Inspector.Platform> Win 10 (64-bit)
User: user
Computer: computer
Virtual Memory: 0.00 MB
Free Disk Space: 374.90 GB
Exe Built: May 7 2016 15:20:25
Init: 000003FF 00000000
App Up Time: 0 days, 0 hours, 0 minutes, 28 seconds
System Up Time: 2 days, 20 hours, 0 minutes, 4 seconds
<CharLogins> 1
<Mem.OomRecoveries> 0
Addon resource usage (not including lua memory): 0
Number of thread pool threads (Total/HighPriority): 4/3
<LauncherName> Battle.net.exe
Session Time(hh:mm:ss): 00:00:23
<SessionTime.Grouping> 00:00:00 - 00:14:59
Time in World(hh:mm:ss): 00:00:10
<TimeInWorld.Grouping> 00:00:00 - 00:14:59
Total Time in World(hh:mm:ss): 00:00:10
<TotalTimeInWorld.Grouping> 00:00:00 - 00:14:59
Total lua memory: 34952KB
<Addons.Current> +Wowhead_Looter
<Addons.Current.Function> GetCollectedShown
<Addons.Current.Object> (null)
<Set.Addons.All.Loaded> +Wowhead_Looter
<Set.Addons.All.Loaded> DuffedUI
<Set.Addons.All.Loaded> DuffedUI_ConfigUI
<Addons.HasAny.Loading> No
<Addons.HasAny.Loaded> No
Number of successful WoWConnections: 7
<Realm.Name> Beta Leveling Realm 01
<Realm.IP> 199.108.44.11:3724
<Realm.Flags> 0x00

Second one appears in Azsuna in Ruins of Nar'thalas. This one is only a Lua-error.
Error:
Message: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:3468: attempt to perform arithmetic on local 'firstFloor' (a nil value)
Time: 05/14/16 21:50:44
Count: 3
Stack: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:3468: in function `wlGetLocation'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:751: in function `wlRegisterUnitLocation'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4107: in function <Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4058>

Locals: zone = "Ruins of Nar'thalas"
mainZone = "BrokenShore"
_ = 667
_ = 667
isMicroZone = false
microZone = nil
currentDL = 0
currentId = 1021
wasMicroZone = false
oldMicroZone = nil
x = 0
y = 0
dl = 0
floorMapCount = nil
firstFloor = nil
(*temporary) = ""
(*temporary) = 5
(*temporary) = 0
(*temporary) = false
(*temporary) = 1220
(*temporary) = 0
(*temporary) = 2
(*temporary) = "attempt to perform arithmetic on local 'firstFloor' (a nil value)"
GetRealZoneText = <function> defined =:-1
GetCurrentMapDungeonLevel = <function> defined =:-1
SetMapToCurrentZone = <function> defined =:-1
GetInstanceInfo = <function> defined =:-1
WL_ZONE_EXCEPTION = <table> {
ShrineofSevenStars = 905
ShrineofTwoMoons = 903
}
GetPlayerMapPosition = <function> defined =:-1
GetNumDungeonMapLevels = <function> defined =:-1
SetDungeonMapLevel = <function> defined =:-1
DungeonUsesTerrainMap = <function> defined =:-1
floor = <function> defined =:-1

Post by tymesink

I got errors as well...

Message: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:3468: attempt to perform arithmetic on local 'firstFloor' (a nil value)
Time: 05/14/16 17:51:23
Count: 2
Stack: Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:3468: in function `wlGetLocation'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:751: in function `wlRegisterUnitLocation'
Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4107: in function <Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:4058>

Locals: zone = "Broken Shore"
mainZone = "BrokenShorePaladin"
_ = 0
_ = 0
isMicroZone = false
microZone = nil
currentDL = 0
currentId = 1031
wasMicroZone = false
oldMicroZone = nil
x = 0
y = 0
dl = 0
floorMapCount = nil
firstFloor = nil
(*temporary) = "Normal Scenario"
(*temporary) = 1
(*temporary) = 0
(*temporary) = false
(*temporary) = 1500
(*temporary) = 5
(*temporary) = 2
(*temporary) = "attempt to perform arithmetic on local 'firstFloor' (a nil value)"
GetRealZoneText = <function> defined =:-1
GetCurrentMapDungeonLevel = <function> defined =:-1
SetMapToCurrentZone = <function> defined =:-1
GetInstanceInfo = <function> defined =:-1
WL_ZONE_EXCEPTION = <table> {
ShrineofSevenStars = 905
ShrineofTwoMoons = 903
}
GetPlayerMapPosition = <function> defined =:-1
GetNumDungeonMapLevels = <function> defined =:-1
SetDungeonMapLevel = <function> defined =:-1
DungeonUsesTerrainMap = <function> defined =:-1
floor = <function> defined =:-1

Post by yoshimo

GetNumDungeonMapLevels() now returns a list of available map levels instead of
a total count.
that might cause the issues with the floor level being off

Post by Erorus

If the WoW executable crashes, that's not on us, please report it to Blizzard through their beta feedback mechanisms. Lua should not be able to crash the client, no matter what. That's something Blizzard will have to fix.

Regarding the Lua errors, we have someone looking into updating the addon for Legion beta, and we hope to post fixes for it soon.

Thanks for reporting your issues.

Post by Nulgar

A friend who was in the Alpha already had crashes after certain builds, he said using the "Scan and Repair" function in the Launcher helped, probably due to some corrupted files.
Could help in this case, too.

Lua should not be able to crash the client, no matter what.

Well, it's not exactly a crash, but I've encountered at least one addon (some Archaeology addon, maybe another as well) that somehow got you stuck on the loading screen with a full bar.

Post by liquidbasex

If the WoW executable crashes, that's not on us, please report it to Blizzard through their beta feedback mechanisms. Lua should not be able to crash the client, no matter what. That's something Blizzard will have to fix.

Not completely correct.
The crash is caused by the function GetCollectionShown() accessed by even the wowheadlooter. With Legion is for this function yet a further variable gotten, which is not yet available at the AddOn.
It is the following variable:
C_TransmogCollection.GetCollectedShown()

@Nulgar
The "Scan and repair"-function do not work for the crit-error-issue.

Two issues with WoWheadlooter on current beta 7.0.3

Post Reply