Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

desync logs #2374

Closed
wzdev-ci opened this issue Dec 2, 2010 · 8 comments
Closed

desync logs #2374

wzdev-ci opened this issue Dec 2, 2010 · 8 comments

Comments

@wzdev-ci
Copy link
Contributor

wzdev-ci commented Dec 2, 2010

resolution_fixed type_bug | by Terminator


master-20101201
desync during lots of units moving (at a time when a huge "zerg" moves)

if not a camera moving bug - seem like master goes to the next step =)


Issue migrated from trac:2374 at 2022-04-16 06:50:45 -0700

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 2, 2010

Terminator uploaded file logs_some_desync.zip (218.9 KiB)

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 2, 2010

Terminator uploaded file logs_NTW_huge armies_desync.zip (901.3 KiB)

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Dec 2, 2010

Terminator commented


added one more logs on NTW map: it was fine until max units production was reached. than de-sync & magic begins.

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jan 7, 2011

Cyp changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jan 7, 2011

Cyp changed resolution from `` to fixed

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jan 7, 2011

Cyp commented


Don't delete pathfinding jobs before execution, even if the result is not wanted.

Pathfinding can return different paths (of the same length), depending on the order of execution of path jobs, due to caching.

This, combined with paths being deleted before execution could cause occasional hard to reproduce desynchs.

Probably fixes #2374.
Changeset: 642bf5ffd00e4f72389b087c92fe0faed21a628c

@wzdev-ci wzdev-ci closed this as completed Jan 7, 2011
@wzdev-ci
Copy link
Contributor Author

Cyp commented


Don't delete pathfinding jobs before execution, even if the result is not wanted.

Pathfinding can return different paths (of the same length), depending on the order of execution of path jobs, due to caching.

This, combined with paths being deleted before execution could cause occasional hard to reproduce desynchs.

Probably fixes #2374.
Changeset: 642bf5ffd00e4f72389b087c92fe0faed21a628c

1 similar comment
@wzdev-ci
Copy link
Contributor Author

Cyp commented


Don't delete pathfinding jobs before execution, even if the result is not wanted.

Pathfinding can return different paths (of the same length), depending on the order of execution of path jobs, due to caching.

This, combined with paths being deleted before execution could cause occasional hard to reproduce desynchs.

Probably fixes #2374.
Changeset: 642bf5ffd00e4f72389b087c92fe0faed21a628c

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant