You must login to post a comment. Don't have an account? Register to get one!

• 

  • #11

  glithramir Mon, 20 Oct 2008 08:39:43

  I did Felmyst and Twins yesterday with full raid. The problem did not appear so I would consider this problem fixed.

  Thanks.

• 

  • #10

  Archarodim Sat, 18 Oct 2008 11:36:09

  Can you confirm me the problem is fixed?

• 

  • #9

  glithramir Wed, 15 Oct 2008 07:35:19

  I tried Beta 3 yesterday. Wasnt a "hard" raid, we only did vashj but I didnt get the same problem as before. Maybe I was lucky or you solved the problem.

  Thanks.

• 

  • #8

  glithramir Tue, 14 Oct 2008 10:05:13

  I didnt reconfigure the prio list after installing the beta. And that would answer why I never saw the previously prioritized members first. I had approx 8 members in the prio list before.

  I will try the new beta 3 and make sure the prio list is cleared tonight.

  
  

• 

  • #7

  Archarodim Tue, 14 Oct 2008 01:40:06

  Please, try : 2.3 beta 3

• 

  • #6

  Archarodim Mon, 13 Oct 2008 21:59:05

  Note that since the version 2.3 beta, the internal priority and skip list format has changed, the first time you install 2.3, the priority and skip list are cleared.

  So did you re-configure your priority list since you installed this beta?

  - Are you using names in the list or group/class?
  - How many players are in the priority list?

  Something you can try is to not use the priority list at all and see if it still crashes ; use the 'C' button on the list interface to clear it (or just remove every one)

  Thank you

• 

  • #5

  glithramir Mon, 13 Oct 2008 19:22:31

  We were 25ppl in the raidgroup when it happened.

  I have a prio-list but now that you mention it, it didnt seemed to work. I always was on the first position but the ppl on priolist should have been listed first. There wasnt a raid today so I havent been able to do more testing. I hope you can have some ideas where the problems comes from anyway. If you want me to try something I can try it tomorrow during raid.

• 

  • #4

  Archarodim Mon, 13 Oct 2008 11:16:21

  Ok the massage indicates that this happens when Decursive scans the raid group.

  Are you using the priority and/or the skip list?
  How many characters were in your raid group?

• 

  • #3

  glithramir Sun, 12 Oct 2008 17:48:01

  Date: 2008-10-12 19:28:32
  ID: 2
  Error occured in: Global
  Count: 1
  Message: ..\AddOns\Decursive\Dcr_DebuffsFrame.lua line 470:
     stack overflow
  Debug:
     Ace2\AceEvent-2.0\AceEvent-2.0.lua:369:
        Ace2\AceEvent-2.0\AceEvent-2.0.lua:345
  

• 

  • #2

  glithramir Sat, 11 Oct 2008 22:31:30

  I do get an error message which states that is it Decursive(I'm sorry but the WoW-client totaly freeze so i cant copy the message). I have not experiensed any problems after i removed Decursive.

  For a while is more about 30minutes. I have gotten the problem both out of combat and in combat. It was "2.3_Beta_2-1-g702d8a1" I tried if i remember correctly.

  I'll install it again and try and write down the error message.