Recycling of object IDs
Bug #329874 reported by
Manuel Moos
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Armagetron Advanced |
New
|
Undecided
|
Manuel Moos | ||
| 0.2.8 |
Fix Committed
|
Wishlist
|
Manuel Moos | ||
Bug Description
While more severe problems were fixed recently, the following netobject ID problem still exists. It can happen that:
- a netobject gets destroyed, sending destroy messages to connected peers
- its ID gets recycled for a new object
- the creation message for the new object arrives before the destruction message of the old object, triggering an error on the receiver.
Possible solutions:
- try not to recycle IDs with pending destruction messages
- try not to send object creation messages for objects with IDs with pending destruction messages.
Related branches
Revision history for this message
| Manuel Moos (z-man) wrote | #1 |
| Changed in armagetronad: | |
| assignee: | nobody → z-man |
| Changed in armagetronad: | |
| milestone: | none → 0.4.0 |
To post a comment you must log in.
A fix was committed to 0.2.8. It may have ill side effects, in which case it will be reverted.
Definitely, a proper solution should be developed for the trunk. Pending deletion messages need to be tracked and object IDs used in them must not be reused.