Jump to content

kero99

Members
  • Posts

    157
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Posts posted by kero99

  1. Hi, i have some compile error, my environment is Ubuntu 10.10 server 64bit GCC 4.4.1 - Mangos REV 11382:

    In file included from /root/mangosdev/src/game/WardenMgr.h:27,
                    from /root/mangosdev/src/game/WardenMgr.cpp:19:
    /root/mangosdev/src/game/WorldSession.h:182: warning: unused parameter 'packet'
    /root/mangosdev/src/game/WardenMgr.h: In constructor 'WardenMgr::WardenMgr()':
    /root/mangosdev/src/game/WardenMgr.h:211: warning: 'WardenMgr::m_Banning' will be initialized after
    /root/mangosdev/src/game/WardenMgr.h:207: warning:   'bool WardenMgr::m_HalfCall'
    /root/mangosdev/src/game/WardenMgr.cpp:36: warning:   when initialized here
    /root/mangosdev/src/game/WardenMgr.cpp: In member function 'void WardenMgr::Initialize(const char*, u_short, bool)':
    /root/mangosdev/src/game/WardenMgr.cpp:60: warning: suggest parentheses around assignment used as truth value
    /root/mangosdev/src/game/WardenMgr.cpp: In member function 'void WardenMgr::Update(uint32)':
    /root/mangosdev/src/game/WardenMgr.cpp:123: warning: unused variable 'res'
    /root/mangosdev/src/game/WardenMgr.cpp: In member function 'bool WardenMgr::LoadFromDB()':
    /root/mangosdev/src/game/WardenMgr.cpp:186: error: 'WorldDatabase' was not declared in this scope
    compilation terminated due to -Wfatal-errors.
    make[2]: *** [src/game/CMakeFiles/game.dir/WardenMgr.cpp.o] Error 1
    make[1]: *** [src/game/CMakeFiles/game.dir/all] Error 2
    make: *** [all] Error 2
    

    Solved adding:

    #include "Database/DatabaseEnv.h"

    But i have other compile error... maybe related with PCH:

    In file included from /root/mangosdev/src/shared/Database/DatabaseEnv.h:40,
                    from /root/mangosdev/src/game/WardenMgr.cpp:23:
    /root/mangosdev/src/shared/Database/Database.h: In constructor 'Database::Database()':
    /root/mangosdev/src/shared/Database/Database.h:308: warning: 'Database::m_pingIntervallms' will be initialized after
    /root/mangosdev/src/shared/Database/Database.h:277: warning:   'int Database::m_nQueryConnPoolSize'
    /root/mangosdev/src/shared/Database/Database.h:225: warning:   when initialized here
    /root/mangosdev/src/game/WardenMgr.h: In constructor 'WardenMgr::WardenMgr()':
    /root/mangosdev/src/game/WardenMgr.h:211: warning: 'WardenMgr::m_Banning' will be initialized after
    /root/mangosdev/src/game/WardenMgr.h:207: warning:   'bool WardenMgr::m_HalfCall'
    /root/mangosdev/src/game/WardenMgr.cpp:37: warning:   when initialized here
    /root/mangosdev/src/game/WardenMgr.cpp: In member function 'void WardenMgr::Initialize(const char*, u_short, bool)':
    /root/mangosdev/src/game/WardenMgr.cpp:61: warning: suggest parentheses around assignment used as truth value
    /root/mangosdev/src/game/WardenMgr.cpp: In member function 'void WardenMgr::Update(uint32)':
    /root/mangosdev/src/game/WardenMgr.cpp:124: warning: unused variable 'res'
    /root/mangosdev/src/game/WardenMgr.cpp: In member function 'void WardenMgr::SendLoadModuleRequest(WorldSession*)':
    /root/mangosdev/src/game/WardenMgr.cpp:520: error: invalid use of incomplete type 'struct WorldSocket'
    compilation terminated due to -Wfatal-errors.
    make[2]: *** [src/game/CMakeFiles/game.dir/WardenMgr.cpp.o] Error 1
    make[1]: *** [src/game/CMakeFiles/game.dir/all] Error 2
    make: *** [all] Error 2

    Best Regards

  2. Core Version : 11064 but is old bug since 9500+

    Patch: RSA fork now but clean when appear in 9500+

    Problem:

    For some reason when pet id in characters_pet become over some number of 170XXXXX (actually our last pet have id 17043690), all new pet tamed or learned by warlock become "Unknow Entity" (in my case "Entidad Desconocida"):

    [sCREENSHOT REMOVED - DO NOT POST SCREENSHOTS OF COPYRIGHTED CONTENT]

    In the other realms with max pet id 15622086 or less, the problem dont appear.

    A year ago this problem appeared at same number of id and we solved it with a wipe of pets, because i thought in a corrupted data in my db...

    Is strange because pet_id value in DB is int 11 and Objectguid maybe is enougth for these values...

    Any ideas?

  3. But RAM usage went down from 28GB to 9GB; so not really sure what those images should tell us.

    Is only that to test undergarun restart mysql service and innodb flush all cache in memory... in some days RAM go up to 28 again :P... innodb cached memory can be set in my.cnf.

    Maybe undergarun show us CPU per thread usage with new db layer, in old layer you can see a big usage of one character mysql connections ( CPU1=68% ) and now you can see two of then (CPU1=31%, CPU3=19%)

    Best regards

  4. Hi all, i found in some freeze crashdump (for example http://pastebin.com/Cb38Lmg6) that in thread 7 of crash dump a strange case with spell 13585 (http://www.wowhead.com/spell=13585) in RemoveAuraHolderFromStack:

    #0  0x000000000088234d in Unit::RemoveAuraHolderFromStack (
       this=0x7fff035e8100, spellId=0, stackAmount=0, 
       casterGUID=17379391082114100824, mode=AURA_REMOVE_BY_DISPEL)
       at ../../../src/game/Unit.cpp:4905
    No locales.
    #1  0x0000000000889d9e in Unit::RemoveAuraHolderDueToSpellByDispel (
       this=0x7fff035e8100, spellId=13585, stackAmount=2, 
       casterGUID=17379391082114100824, dispeler=0x26b30000)
       at ../../../src/game/Unit.cpp:4822
           spellEntry = 0x7fffe676aa00
    

    Could be related this with some freezes? or is only a casuality?

    Best regards

  5. Derex Finally solved the problem: 48h without ACE crashes :

    0ab04bd1b0624640ec3e108bd12508829be51ad6
    src/game/WorldSocket.cpp |    1 +
    1 files changed, 1 insertions(+), 0 deletions(-)
    
    diff --git a/src/game/WorldSocket.cpp b/src/game/WorldSocket.cpp
    index 8b59038..667b039 100644
    --- a/src/game/WorldSocket.cpp
    +++ b/src/game/WorldSocket.cpp
    @@ -445,6 +445,7 @@ int WorldSocket::handle_close (ACE_HANDLE h, ACE_Reactor_Mask)
            m_Session = NULL;
        }
    
    +    reactor()->remove_handler(this, ACE_Event_Handler::DONT_CALL | ACE_Event_Handler::ALL_EVENTS_MASK);
        return 0;
    }
    

    Original code from: https://github.com/TrinityCore/TrinityCore/commit/45459bed23b78fc619475ee2177e826ae4494cd7

    Best regards

  6. As I see, everyone are so scared after commits [10688] and [10677] so noone is willing to test similar patches anymore :D Ok, let's go another way: if you want more patches from me, test this one :P

    I can test patch but need first some days to finish with Reloc branch1 test :P... Soo much amazing patches to test in few days!!!! hehehe

  7. Your crash is not related with Ambal patch, this crash is from mtmaps patch and concurrent access to DB Functions (damned windows dumps..).

    At the moment you still need TBB Concurrent Vector patch (prevent crashes by corruption pointer in targets) and SQLAsynq patch (Prevent crashes in SQL Functions concurrent access) in MTMaps thread to work more or less stable in MapUpdate.Threads = 2 or more.

    And then you will see than MTMaps still dont enought stable :P... but we needed ^^

    Best regards

  8. Hi all, here my feedback in about 1 week testing with default patch config:

    Visibility.RelocationLoverLimit = 10

    Visibility.AIRelocationNotifyDelay = 1000

    And:

    Visibility.GroupMode = 0

    Visibility.Distance.Continents = 90

    Visibility.Distance.Instances = 120

    Visibility.Distance.BGArenas = 180

    Visibility.Distance.Object = 100

    Visibility.Distance.InFlight = 100

    Visibility.Distance.Grey.Unit = 1

    Visibility.Distance.Grey.Object = 10

    MTMaps Actived? Not active for good CPU testing

    Clean Core? No, some patches

    Playerlimit to testing: 2000

    Core Server (DB in other server): Intel Bi Xeon X5650 2 x 6 x 2 x 2.66+GHz - 24GB DDR3 ECC RAM - Ubuntu Server 9.10

    Result:

    HTOP CPU Usage with 2000 Players WITHOUT Visibility and Reloc simplified: 95 - 100% -> ~98%

    HTOP CPU Usage with 2000 Players WITH Visibility and Reloc simplified: 75 - 98% -> ~87%

    Max gain of CPU ~20%

    Standard gain: ~11%

    Minimal gain: ~2%

    Some problem in gameplay detected by testers? No

    Some problem in stability? No

    Conclusion: The patch is really good and help soo much in CPU Usage

    Best regards

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use