24 - Skillet will cause *terrible* lag problems (lock up Wow)
What steps will reproduce the problem?
1. Open the skillet window after you've learned a new item, or a patch has hit, etc. I'm not entirely sure what causes it, since sometimes the lag is very brief, and other times awful.
2.
3.
What is the expected output? What do you see instead?
I expect the Skillet crafting window to pop right up, fully populated. Instead the window pops up but won't have anything in it, and WoW will sit frozen for minutes (I just tested with the 3.0.9 patch and it was about 6 minutes of lock-up), then WoW will briefly flash some activity, and will immediately disconnect.
What version of the product are you using?
1.13-153
Do you have an error log of what happened?
No
Please provide any additional information below.
It looks like Skillet is querying large amounts from the server.
- 3 comments
- 3 comments
Facts
- Last updated
- Mar 30, 2012
- Reported
- Feb 11, 2009
- Status
- Fixed - Developer made requested changes. QA should verify.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- Votes
- 1
- Reply
- #3
Halya Aug 20, 2009 at 23:05 UTC - 0 likesThe behaviour I described in my previous comment is still present in latest release, admittedly, only on my Jewelcrafter is it that bad it will lock up the game until it is done, resulting only in a disconnect. This only 1 single time the first time Skillet is launched after cache has been cleared.
The sheer volume of designs is probably why it displays this behaviour. Other tradeskills do not trigger this reaction or at least not in such a detrimental way
- Reply
- #2
Halya Aug 06, 2009 at 21:34 UTC - 0 likesHi,
I'm a long time skillet user and this has been the standard behaviour of skillet since its existance. This especially rough on jewelcrafters because of the sheer volume of recipes the skill has.
This behaviour is directly related to the Cache of your WoW instance.
Upon the release of a new patch the WoW client cache is flagged as invalid and thus cleared. You can reproduce the behaviour by clearing your cache manually.
Upon the first start of skillet it will scan your entire tradeskill. This will cause WoW to consume a huge amount of CPU and it gets so bad it can stop the client from communicating with the realm. Once the full scan is complete(if you are patient enough to allow it) you often find yourself disconnected because of the time it took (while not having an active comm link to the realm).
Once this initial scan has been completed the response time of skillet is as good as the standard UI.
- Reply
- #1
sn0n Jun 22, 2009 at 10:17 UTC - 0 likesi think this is related to ackis recipe list. as mentioned in another ticket