-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Found a BUG that caused the server to crash.[Bug] #225
Comments
Ok,I will debug it. |
Later, I researched it and found out that the problem was that as long as the character was charmed, ran away in fear, transformed into a small animal, etc., the server would go down. |
quest id? |
14293 |
Can you post crash log? |
I didn't compile the debug. I'll compile a copy today. |
Any crash logs from logs folder? |
the release is not Any crash logs from logs folder。can you test it? |
I'm going to check this debug log on the office computer on Monday. |
Application Log Assertion Failure - worldserver.exe Expression: (low.x <= high.x) && (low.y <= high.y) && (low.z <= high.z) Assertion Failure - worldserver.exe Expression: ! low.isNaN() && ! high.isNaN() Assertion Failure - worldserver.exe Expression: (low.x <= high.x) && (low.y <= high.y) && (low.z <= high.z) Assertion Failure - worldserver.exe Expression: ! low.isNaN() && ! high.isNaN() Assertion Failure - worldserver.exe Expression: (low.x <= high.x) && (low.y <= high.y) && (low.z <= high.z) Assertion Failure - worldserver.exe Expression: ! low.isNaN() && ! high.isNaN() Assertion Failure - worldserver.exe Expression: (low.x <= high.x) && (low.y <= high.y) && (low.z <= high.z) Assertion Failure - worldserver.exe Expression: ! low.isNaN() && ! high.isNaN() Assertion Failure - worldserver.exe Expression: (low.x <= high.x) && (low.y <= high.y) && (low.z <= high.z) Assertion Failure - worldserver.exe Expression: ! low.isNaN() && ! high.isNaN() |
There is only so much for this log file to be recorded. The following error message is not logged. |
Seems gameobject issue |
I think it's also a matter of roles. Once the play is controlled, the server goes down. |
Did you test it later? Have you found the reason for the downtime? I took a look at gameobject.cpp. I didn't see anything wrong. |
Thank you! I'm currently on vacation. I'll try it in about 4 days. |
I found that your source code has the same bug as pandaria, when you buy more than 200,000 gold coins at one time, the gold will not be deducted. |
Yes.We fork from alexkulya's source and have most same bugs. |
How to reproduce? use battle coin buy gold coins? |
No, for example, if I buy 2,200 gold coins at one time, the total amount of gold required is 220,000 gold. However, no gold will be deducted. I think it should be an issue with int32 limitations |
Buy-ins above 2147483647 will not be deducted for gold. This is exactly the upper limit of 32 bits |
I push a commit due to money limit. Try last commit |
How did you find it. The way I came up with was to change the upper limit of the MAX_MONEY_AMOUNT |
MAX_MONEY_AMOUNT is uint64. |
Yes, it is 64 bits, and the values can be large. |
The 32bit uint32 limit is caused by code. DB column is also right. |
You just have to find the specific location. |
For advice, this version of the item upgrade is only up to level 4, and I remember that the official uniform has level 6 or 8. Do you know how to modify the location. |
Could you find some wowhead or old wiki links for me? |
I have a wiki here, but I don't think it's very useful. https://warcraft.huijiwiki.com/wiki/%E9%A6%96%E9%A1%B5 |
https://wowpedia.fandom.com/wiki/Patch_5.4.8 |
I think this source code should have been modified. But I can't find the location where this item was upgraded, and the database hasn't found it either. I think it should be in DBC. |
🐛 Bug report
Found a BUG, in the copy of Blackstone Abyss, boss's creature_template entry: 9018. When the blood hit about 30%, it appeared: unable to attack in escape state. Then the server crashed. At the same time, there are still many tasks that cannot be completed in dialogue with NPC.
Expected behavior
Steps to reproduce
Version
Client Version:
The text was updated successfully, but these errors were encountered: