Critical Error when EPGP is enabled on login.

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Having the addon enabled before login, enabling through addon control
panel after login however, and it works fine.
2.
3.

What is the expected output? What do you see instead?

I expect to be able to log in without first disabling the addon. As of
5.5.10 it crit errors my game as long as it is enabled before login.

What version of the product are you using? What locale is your client (en,
ru, kr, ch, es, tw)? What other addons do you have installed and what
versions? How many members do you have in your guild? (/guildinfo).

Paste the text surrounded by -EPGP- in Guild Information here:

If this is about http://www.epgpweb.com integration, what is the realm
and region of your guild?

Please provide any additional information below.

Original issue reported on code.google.com by travisla...@gmail.com on 10 Nov 2009 at 3:34

[GoogleCodeExporter]

Can you paste the error please?

Original comment by evlogimenos on 10 Nov 2009 at 9:10

[GoogleCodeExporter]

I have the same issue with the latest version ( 5.5.13  ). It crashes the game 
client
throwing out an error about memory read errors.

EN locale, 265 members in guild.

Original comment by sebastar...@gmail.com on 9 Dec 2009 at 10:34

[GoogleCodeExporter]

Can you verify this is epgp that is causing the problem? Try logging in with 
epgp 
enabled only. If that is causing an error can you copy/paste it or screenshot 
it?

Thanks!

Original comment by evlogimenos on 10 Dec 2009 at 12:08

[GoogleCodeExporter]

It's working for me again now. I do think it was in combination of another addon
(though I haven't found which one yet).

Original comment by sebastar...@gmail.com on 11 Dec 2009 at 3:35

[GoogleCodeExporter]

I have this problem. My game crashes when i have both EPGP 5.5.13 and Recount 
3.3b.
If i uninstall Recount, then epgp works okay

Original comment by Kayse...@gmail.com on 16 Dec 2009 at 6:11

[GoogleCodeExporter]

I also have the same problem with EPGP 5.5.13.

I have been running smoothly for over a week now with no crashes and without 
the mod 
enabled. As soon as I enable it and login, it crashes with a memory error.

EPGP is the only mod I have that is showing as out of date.....

Original comment by hom...@globalnet.co.uk on 21 Dec 2009 at 2:18

[GoogleCodeExporter]

Post the error or a screenshot.

Original comment by dingochavezz@gmail.com on 21 Dec 2009 at 2:23

[GoogleCodeExporter]

Out of date doesn't mean much. Can you show a screenshot/paste the error?

Original comment by evlogimenos on 21 Dec 2009 at 7:22

[GoogleCodeExporter]

Issue 560 has been merged into this issue.

Original comment by evlogimenos on 21 Dec 2009 at 7:23

[GoogleCodeExporter]

I will post the data tonight when I get home, but from what I remember, its a 
lot of 
data :-S

Original comment by hom...@globalnet.co.uk on 22 Dec 2009 at 8:37

[GoogleCodeExporter]

Myself and my whole guild are having the same issues,the lua errors are causing 
the
msg to pop up prompting to shut the UI down. Is there going to be a 3.3 update 
for epgp?

Original comment by Nick5...@hotmail.com on 25 Dec 2009 at 6:06

[GoogleCodeExporter]

Its not the version number causing the problem, load out of date addons (from 
the
character selection addon menu) is all that is needed. Your errors are caused by
somethig else, so get a print out of the lua errors and post them here so it 
can be
solved. 

Original comment by dingochavezz@gmail.com on 26 Dec 2009 at 11:37

[GoogleCodeExporter]

Here is the error. Despite the fact that it mentions Postal, it is interesting 
to
note that I can disable EPGP, load a ton of other ones, and it works fine. I've 
had
this issue with other addons (recount, to name one) as well. 

==============================================================================
World of WarCraft (build 11159)

Exe:      D:\Program Files\World of Warcraft\WoW.exe
Time:     Jan  4, 2010 10:05:42.449 PM
User:     
Computer: 
------------------------------------------------------------------------------

This application has encountered a critical error:

Not enough storage is available to process this command.

Program:    D:\Program Files\World of Warcraft\WoW.exe
File:   .\src\lmemPool.cpp
Line:   311

Requested 6144 bytes of memory

WoWBuild: 11159
Realm: Aerie Peak [213.248.123.43:3724]
Local Zone: Dalaran City, Dalaran
Local Player: ******, 0500000000C409CF, (5742.03,678.97,644.743)
Total lua memory: 52775KB
Current Addon: Postal
Current Addon function: FixFrameLevel
Current Addon object: (null)
Add Ons: Altoholic aSettings Auc-Advanced Auc-Filter-Basic Auc-Stat-Classic
Auc-Stat-Histogram Auc-Stat-iLevel Auc-Stat-Purchased Auc-Stat-Simple 
Auc-Stat-StdDev
Auc-Util-FixAH Bartender4 BasicChatMods BeanCounter cargBags cargBags_Nivaya 
CLCRet
DataStore DataStore_Achievements DataStore_Auctions DataStore_Characters
DataStore_Containers DataStore_Crafts DataStore_Currencies DataStore_Inventory
DataStore_Mails DataStore_Pets DataStore_Quests DataStore_Reputations
DataStore_Skills DataStore_Spells DataStore_Stats DataStore_Talents DoTimer 
Elephant
EnsidiaFails epgp Informant Ace3 Omen OmniCC oRA2 oUF Outfitter PallyPower 
Postal
Recount SpartanUI SpartanUI_FilmEffects SpartanUI_PartyFrames 
SpartanUI_PlayerFrames
SpartanUI_SpinCam Stubby !Swatter TankPoints XRS DBM-Core 

Original comment by sebastar...@gmail.com on 4 Jan 2010 at 9:11

[GoogleCodeExporter]

Thanks everyone for the bug reports. Unfortunately this issue cannot be 
resolved by 
me. No addon should be able to crash the client, this is a client bug so you 
need to 
poke Blizzard Tech Support.

I have looked into this a bit (googled it). Blizzard Tech Support suggested the 
following:
* removing the cache folder and trying again
* removing the wtf folder and reconfiguring your addons from scratch
* repairing the client
* reinstalling the game and all patches from scratch

Original comment by evlogimenos on 5 Jan 2010 at 9:31

• Changed state: WillNotFix

[GoogleCodeExporter]

Original comment by evlogimenos on 5 Jan 2010 at 9:31

[GoogleCodeExporter]

I completely uninstall wow today and reinstall thinking the client had become
corrupt. only to fined the the same error is still happening. The only addon I 
had
installed was X-Perl.. I enabled EPGP and started crashing again. Anyway here 
is the
error report.. I hope this may help

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal Exception
Program:    E:\World of Warcraft\WoW.exe
Exception:  0xC0000005 (ACCESS_VIOLATION) at 001B:00833506

The instruction at "0x00833506" referenced memory at "0x0000000D".
The memory could not be "read".

WoWBuild: 11159
Realm: ********* 
Local Zone: The Eventide, Dalaran
Local Player: *******, 05000000024CE965, (5689.22,662.161,646.422)
Total lua memory: 14742KB
Current Addon: (null)
Current Addon function: UNKNOWN
Current Addon object: (null)
Add Ons: CoolLine epgp XPerl XPerl_ArcaneBar XPerl_PartyPet XPerl_Party
XPerl_PlayerBuffs XPerl_PlayerPet XPerl_Player XPerl_RaidAdmin XPerl_RaidHelper
XPerl_RaidMonitor XPerl_RaidPets XPerl_RaidFrames XPerl_TargetTarget 
XPerl_Target 

Original comment by cfor...@hotmail.com on 6 Jan 2010 at 12:22

[GoogleCodeExporter]

Issue 550 has been merged into this issue.

Original comment by evlogimenos on 10 Jan 2010 at 8:47

[GoogleCodeExporter]

For me the issue has been resolved by deleting the Cache, WDB and WTF folders. 
After
deleting and restarting WoW I naturally had to reconfigure my entire UI and 
addons,
but I have not had any crashes since then.

Original comment by sebastar...@gmail.com on 10 Jan 2010 at 1:09

[GoogleCodeExporter]

@sheuk : Lots of people in my guild have had this problem and done the same 
thing you
have only for the same error to return in a few days. Blizzard will no doubt 
patch it
by the 5th expansion ;)

Original comment by dingochavezz@gmail.com on 10 Jan 2010 at 6:07

[GoogleCodeExporter]

I'm having the same issue. Looks like it is related with epgp.lua on 
SavedVariables.
When have too much entries there the game crashes on start. Maybe have option 
to wipe
the log completely not only older than one month.

Original comment by henrique...@gmail.com on 24 Jan 2010 at 1:13

[GoogleCodeExporter]

Unfortunatly more and more members of the guild are having problems. It is 
getting 
to the stage where very few raid leaders can use this.

Regardless of if this is a mod or blizzard problem, it would be better for you 
(the 
mod writer/maintainer) to communicate to Blizzard about it as you know what you 
are 
talking about having written the mod.

Original comment by hom...@globalnet.co.uk on 25 Jan 2010 at 12:09

[GoogleCodeExporter]

I have a log going back 6 months, I get the same wow crash error regardless of 
which
addons are turned on or off, its not EPGP thats the problem, its some bug 
Blizzard
introduced in the latest patch.

Most of the time the errors occur when moving between zones - flying out of 
Dalaran
is a big one for me.

Original comment by dingochavezz@gmail.com on 25 Jan 2010 at 6:47

[GoogleCodeExporter]

@dingochavezz
Then I would suggest that your problem is something completly different to mine.

If the EPGP mod is loaded on logging then I can almost guarantee this error and 
yet 
if I disable this mod, then I can guarentee that the error will no0t occur.

I am not saying that this is a problem with the EPGP mod and could easily be a 
problem that Blizzard have introduced, but the problem is between Blizzard and 
the 
EPGP mod and therefor would be better for the mod owner to discuss this issue 
with 
Blizzard rather than each individual having the problem.

I have been running fine for weeks now without having the EPGP mod running. I 
still 
have DBM, Recount, Pallypower and raremobs mod loding and these have not caused 
me 
to crash at all.

Original comment by hom...@globalnet.co.uk on 26 Jan 2010 at 12:20

[GoogleCodeExporter]

@henrique.andreassy
  You can do what I do with trimming the log file.  1 month is just to much for me, I
don't need all that.  Here are the steps to change this.

1. Open "...\World of Warcraft\Interface\AddOns\epgp\log.lua" with write
2. Search for "  local last_timestamp = GetTimestamp({ month = -1 })"
3. Change to "  local last_timestamp = GetTimestamp({ day = -7 })" This remove
anything older then 7 days from the log. 
3. You can also use the following if you wish.

  local last_timestamp = GetTimestamp({ day = -1 })
  local last_timestamp = GetTimestamp({ hour = -12 })
  local last_timestamp = GetTimestamp({ day = -14 })

I myself use 'hour = -12'.  I upload my epgp.lua to my website where it parses 
and
stores all the logs to be viewed.

Original comment by black.ca...@gmail.com on 26 Jan 2010 at 9:26

[GoogleCodeExporter]

We do not use the logs at all as it would be too much hassle to merge from all 
the 
raid leaders. Is it possible to switch the logs off through the interface or 
even 
change how much to keep through the interface ?

I have my suspisions that the error is caused between this and the recount log 
.....

Original comment by hom...@globalnet.co.uk on 27 Jan 2010 at 12:14

[GoogleCodeExporter]

@hom.... If Blizzard introduce an error that causes a problem, then they are 
more
likely to take notice of a lot of people reporting the issue, than one addon
developer reporting it. They listen to the masses not the minority.

If you are a developer (since you seem to have figured out its something to do 
with
recount now) then how about posting an error.

Btw, I have DVE, Recount, BigWigs, Skada, Omen, PallyPower, Raid Buff Status, 
EPGP,
EPGP Lootmaster, Bartender, PitBull4, ThreatPanels, Utopia, ZOMG, Auctioneer, 
ORA3
and about 20-30 other addons running and hardly ever get any errors. The only 
error I
do get is a WOW Crash caused when zoning and its with or without EPGP running 
that it
occurs. They usually occur when getting close to Dalaran or just leaving 
Dalaran.

Original comment by dingochavezz@gmail.com on 27 Jan 2010 at 12:39

[GoogleCodeExporter]

I will post about this in the europe forums, but as you most likely know, 
Blizzard 
support for developers on the european forums is lacking at the very least. It 
is better if 
you post this on the US forums and generate some noise.

Original comment by evlogimenos on 27 Jan 2010 at 3:43

[GoogleCodeExporter]

Let me add some information that MAY be helpful:

1)  the issue is absolutely epgp-only related.  I have invested significant 
time 
unistalling & reinstalling ... deleting cache, wtf files ... and testing with 
epgp 
on and not on.  My system ONLY crashes when epgp is on, although if epgp is the 
only 
mod running, my system will handle it.

2)  the behavior of my system changes depending whether epgp is enabled or not 
upon 
login.  If I log on with epgp and manage not to crash, my entire game freezes 
for a 
moment as if it is trying to process a massive amount of information.  This 
happens 
if epgp is the only mod or if all my mods are on.  If I disable epgp, the 
momentary 
freeze disappears.

3)  I scoured the blizzard forums for common variables between people having 
the 
same problem, and it always seemed to involve computers running Windows 7 
64bit.  
This could be unrelated, but it appeared to always be a commonality.

In short, it appears that epgp is trying to process too much information of 
some 
sort upon login that causes the crash.   I love my epgp but cannot run it 
without 
running a risk of crashes.  Hoping you CAN find a fix ...

CHeers

Original comment by lyphemob...@gmail.com on 27 Jan 2010 at 9:45

[GoogleCodeExporter]

I am not saying it is not EPGP that causes the crash. What I am saying is that 
*no* 
addon should be able to be crashing the client. In the same way that no website 
should be able to crash your browser.

To top it off, the error gives me no information on how to fix the problem. It 
says "oh 
I couldn't allocate this much ram, boom". That doesn't help all that much. You 
can try 
to trim your logs; for some it worked, for others it didn't. It's all hit and 
miss so I 
didn't recommend any solution.

To top it off, I did not see this problem ever (I run a Mac btw - maybe this is 
a 
Windows only bug). So even with the limited information at hand, it is 
impossible for 
me to fix this problem, since I cannot even reproduce it.

This is where you come in. Make a thread, link it here and have people add 
their 
results to the thread and get the attention of the developers. Only then they 
will fix 
this.

Original comment by evlogimenos on 27 Jan 2010 at 9:55

[GoogleCodeExporter]

It not windows 7 specific. I personally am still on XP. The problem started 
occuring 
with the release of patch 3.3 and the upgrade of mods to go with that, I doubt 
many 
people upgraded windows and patch 3.3 at the same time.

I agree with the foillowing comment :-
**What I am saying is that *no* 
addon should be able to be crashing the client**

The problem I have is that what I use in the mod is very simple. I have no need 
for 
large logs or anything else, so what is the EPGP mod loading in to memory when 
wow 
loads up ?

Also, people have mentioned about cutting the log down, personally I would be 
happy 
to wipe it every time I enter wow if thats what is needed as a temporary 
measure, 
but I do not know how to do this.

Finally, I am a developer and have an idea about how to test, debug etc. But I 
know 
nothing about developing wow mods and have never had the time to look into it.

If you could tell us what EPGP is loading, then maybe it would be possible to 
disable this on a mod parameter setting ?

Original comment by hom...@globalnet.co.uk on 28 Jan 2010 at 12:22

[GoogleCodeExporter]

First off.. I have NEVER had a crash.. EVER since starting EPGP about 2 months 
ago.

My system:
- Win Vista
- 4 gigs ram
- Nvidia 250

I run a large amount of addons, about 100 give or take. 244 directories in my 
addon
folder not counting Blizzard_*.  Several are disabled..  At the time of this 
post my
addons are using about 66MB of memory.

1. Auc-ScanData = 11.36 MB
2. Informant = 5.67 MB
...
17. EPGP = 752 KB
...
37. EPGP_lootmaster_ml = 340 KB
...
41. EPGP_lootmaster = 234 KB 

I have a hard time thinking its JUST EPGP causing the crashes.  From past 
experience
with computers and programming.. This appears to be a soft mixed with computer 
setups.

Original comment by black.ca...@gmail.com on 29 Jan 2010 at 1:28

[GoogleCodeExporter]

Since the latest patch 3.3.2 the crash has not occured for me, or anyone else 
in the
guild. We are getting the usual lag disconnects after a major patch, but no more
error, so looks like Blizzard fixed the bug they introduced.

Original comment by dingochavezz@gmail.com on 4 Feb 2010 at 6:36

[GoogleCodeExporter]

Can more people verify this?

Original comment by evlogimenos on 5 Feb 2010 at 12:27

[GoogleCodeExporter]

20+ people in my guild can confirm it so far.

Original comment by dingochavezz@gmail.com on 5 Feb 2010 at 12:55

[GoogleCodeExporter]

To clarify that: EPGP is compulsory for all my guild members, they have it or 
they
get no loot. No crashes at all with the memory error from any of them, before 
that it
was a regular thing occuring for most of the guild.

Original comment by dingochavezz@gmail.com on 5 Feb 2010 at 1:07

[GoogleCodeExporter]

The mod now seems to be working ok for us aswell.

Original comment by hom...@globalnet.co.uk on 9 Feb 2010 at 7:28