349 - [Severe Bug] It works while in combat with very high CPU usage.
I label this severe since it is the Number 1 reason for a hard core raider to remove this addon complete or hack it to work otherwise.
Even in Combat the addon inflict VERY high cpu usage e.g. up to 10% according to Broker CPU addon while others don't go above 1%.
It has to be disabled in combat or have an option to be disabled in combat. Actually it appears to be a clear bug since it appears unusable in combat anyway.
UPDATE: It actually is dysfunctional since there is an option at 'Automation' and I have it enabled.
I tested this in a LFR.
| User | When | Change |
|---|---|---|
| fateswarm | Dec 19, 2011 at 12:28 UTC | Create |
- 4 comments
- 4 comments
Facts
- Reported
- Dec 19, 2011
- Status
- New - Issue has not had initial review yet.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- Votes
- 0
Reported by
Possible assignees
-
- Manager
- Author
-
- Author
-
- Translator
- Reply
- #4
fateswarm Dec 26, 2011 at 10:18 UTC - 0 likesI had noticed it in an Ultraxion LFR, if that helps.
That fight is in general a problem in FPS. I wonder if for some reason it doesn't sent 'OOC' related events properly. Or something of the sort.
- Reply
- #3
danielbarron Dec 26, 2011 at 07:54 UTC - 0 likesStrange. I will try and replicate. Thanks.
- Reply
- #2
fateswarm Dec 19, 2011 at 20:07 UTC - 0 likesI wonder if it's an API issue with the detection of OOC since I did not notice it now when a 25man in a LFR at trash.
- Reply
- #1
fateswarm Dec 19, 2011 at 19:59 UTC - 0 likesI wonder if it's a LFR-only issue.