We are migrating issue tracker of Cocos2d-x Project to Github, please create new issue there. Thanks.
invoking CCDirector::sharedDirector()->end() in schedule leads to crashes
invoking CCDirector::sharedDirector()->end() in schedule leads to crashes
Bug #306 [Closed]
- Subject changed from call CCDirector::sharedDirector()->end() in schedule crashes to invoking CCDirector::sharedDirector()->end() in schedule leads to crashes
- Target version set to cocos2d-0.99.5-x-0.7.2
- Assignee set to walzer@cocos2d-x.org
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset commit:“29a6a593fc8e66f31daec5bbf5a273f82b2a3ef0”.
Applied in changeset commit:“29a6a593fc8e66f31daec5bbf5a273f82b2a3ef0”.
Applied in changeset commit:“29a6a593fc8e66f31daec5bbf5a273f82b2a3ef0”.
- Status changed from Resolved to Closed
- Project changed from cocos2d-x to cpp
- Target version deleted (
cocos2d-0.99.5-x-0.7.2)
| Status: | Closed | |
|---|---|---|
| Start date: | 2011-01-06 | |
| Priority: | Normal | |
| Due date: | ||
| Assignee: |  walzer@cocos2d-x.org |
|
| % Done: | 100% |
|
| Category: | - | |
| Target version: | - |
I believe that end() release all resources while schedule will proceed to use these resources’ pointer.
In objc, call [nil method] is safe, but in c++ it will cause crash.
Maybe set a flag in end(), then release resource in the next message loop is a better design.