Forums
-
Temporary category
-
- No posts here yet
-
-
Community
-
- 173
- posts
-
- 524
- posts
-
-
Metin2
-
- 3,554
- posts
-
- 66,706
- posts
-
- 6
- posts
-
- 6,902
- posts
-
- 1,124
- posts
-
- 972
- posts
-
- 11,400
- posts
-
- By felipeard1
-
- 1,272
- posts
-
-
Releases
-
- 487
- posts
-
- 1,544
- posts
-
- 7,111
- posts
-
- 991
- posts
-
- 5,149
- posts
-
- 2,025
- posts
-
- 676
- posts
-
- 358
- posts
-
-
Safe Zone
-
- 1,378
- posts
-
- 259
- posts
-
- 766
- posts
-
-
Who's Online 40 Members, 2 Anonymous, 44 Guests (See full list)
- Tallywa
- Dr3Ame3r
- _Sielu
- DiviDi
- Karbust
- mogulul
- Asdator
- misterioso
- Nixon4Major
- ruizuinho-o
- Evo
- Sonitex
- DrPrefix
- M.Sorin
- Crital
- .ZeNu
- Takuma
- HITRON
- Zerial
- hachiwari
- Owsap
- Sevence™
- Catii
- ImKoksu
- pewi
- payoneer55594
- mustafaxddd
- Achilleee
- iShadoW
- tierrilopes
- AlleXuSS
- MEKA
- ASIKOO
- IGNEEL
- masodikbela
- ondry
- Yazoo
- pask1994
- Flourine
- George
-
Forum Statistics
19,876
Total Topics105,261
Total Posts -
Member Statistics
-
News
-
-
Topics
-
-
Messages
-
The problem actually happens from here: void CWindowManager::Update() { // If this code is commented is working fine. // __ClearReserveDeleteWindowList(); // And add this instead: _ReserveDeleteWindowList.clear(); m_pRootWindow->Update(); } So is happening when the CWindowManager is sending the Update() -> OnUIUpdate (PythonApplication), is not actually easy to follow this func to find what cause the problem, if @Minton could give us more info what he have added in his source and the problem appear would be nice. -
By Distraught · Posted
How was that vector initialized? Never trust on an “i think”. If it’s filled with raw pointers, a clear does not free the memory it points to. If it stores smart pointers than their lifetimes’ are managed. Post the declarations, because there are many more reason for it. What problem you’ve fallen into is called dangling pointers. It occurs when you have invalidated pointers as their memory is freed but they are unable to check because they are not set to nullptr. This can lead to a lot of other error because something is surely not okay there. Don’t hide the errors, solve them as it will just always get worse. The easiest way is to store shared pointers and use weak pointers when you access any of the elements so that you can check their validity. If it’s a common base class consider making it usable with intrusive pointers as the specifications allow. -
.thumb.jpg.7f69b74e7321cafd52be217bc7fe663d.jpg)
#closed If you bought the dungeon from @.plechito' do not hesitate to contact him. I am sure you will get support. Otherwise I assume that you are using a ripped version. Regards
Raylee -
-
https://mega.nz/#!QQlT3QgS!2IhcPojBfzqcNM3_tgG-V9c6JWmptMasCuYebGtKwFA
-
-
Popular Contributors
-
