Client Crash Jeweller Gems

[Voldemmort]

Rev: 9729

When you try to equip 4+ Gems of any jeweller gem you get a client crash, instead of receiving an error, you socket correctly the first 3 Gems, and when you going to try to socket the next gem client crash with Error #132: Fatal Exception ACCESS_VIOLATION.

For example try to equip 4 http://www.wowhead.com/item=36767 and you get client crash.

Or equip 3 http://www.wowhead.com/item=36767 + 1 http://www.wowhead.com/item=36766 and again client crash.

I know you must use only 3 Jeweller gems but to properly report the bug

[Diablox]

I do not see how this is a bug. You can only have 3 gems

[Voldemmort]

The bug is that you got Client Crash, instead of an error or advice in-game, the problem is that I dont know what is exactly blizzlike the error you have to get .

Maybe something like "You can´t equip more than 3 Jeweller Gems"?

[Diablox]

It is a bug with the client not with the server.

[Voldemmort]

I have an account at offi, but not enought lvl to test that out, but I'm pretty sure it is not Client Fault, cause if it was client fault, the client would crash too when having or trying to use more than 1 unique equip item, and this bug has some time on the server.

I'll ask a friend to test that out and see if it is or not client bug.

[darkstalker]

client bugs are caused by the server sending wrong data

[Voldemmort]

client bugs are caused by the server sending wrong data

Yes thats I think the same

[KAPATEJIb]

Bug confirmed with rev 9867

[laise]

client seems to crash if any of these sent :

   EQUIP_ERR_ITEM_MAX_LIMIT_CATEGORY_COUNT_EXCEEDED_IS
           EQUIP_ERR_ITEM_MAX_LIMIT_CATEGORY_SOCKETED_EXCEEDED_IS
           EQUIP_ERR_ITEM_MAX_LIMIT_CATEGORY_EQUIPPED_EXCEEDED_IS

[goodbadguy]

Anyone have a solution for this yet? 6 months and still clients crash when these error messages are supposed to be sent instead.

[VladimirMangos]

it crash not instead but _at_ this messages receive from mangos. Need way send to error message raleted item id.

Possible most easy use way silmilar quest reporting: so have msg = true additional arg and call error report from check code if set. instead return error code from. But sometime we diff way proccess different error codes so this can be also not so clean way

[darkstalker]

no one has sniff with the correct packet structure?