2019-12-07 07:28 CET

View Issue Details Jump to Notes ] Related Changesets ]
IDProjectCategoryView StatusLast Update
0005302Spring engineGeneralpublic2016-07-16 18:25
Reporternixtux 
Assigned Tohokomoko 
PriorityhighSeveritymajorReproducibilityhave not tried
StatusresolvedResolutionfixed 
Product Version102.0 
Target VersionFixed in Version 
Summary0005302: extreme slowdown
Descriptionwatch replay you need to be at least 47mins +
disabling luaiu/luarules has no effect to performance
replay: http://replays.springrts.com/replay/576185574280e7bc3315438c335e4984/
infolog.txt: http://pastebin.com/kCnwjmB2

backlink to TA bug report: https://github.com/n3wm1nd/TA/issues/1121
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0016505

abma (administrator)

output/screenshot of /debug would be VERY useful when it hangs / is this slow.

~0016506

abma (administrator)

Last edited: 2016-07-15 00:38

View 2 revisions

47+ min replay isn't very useful :-|

is there a faster way to reproduce this issue?

~0016507

abma (administrator)

i get ~ 80% cpu usage of Unit::MoveType::Update::Collisions (but only 2ms lag? hu?)

~0016512

hokomoko (developer)

Fix 0354b349a01346422d9ce343c2e76eb4dabb1805 committed to develop branch: Fix 0005302, repo: spring changeset id: 7205
+Notes

+Related Changesets

-Issue History
Date Modified Username Field Change
2016-07-13 16:11 nixtux New Issue
2016-07-15 00:37 abma Note Added: 0016505
2016-07-15 00:37 abma Note Added: 0016506
2016-07-15 00:37 abma Status new => feedback
2016-07-15 00:38 abma Note Edited: 0016506 View Revisions
2016-07-15 00:38 abma Description Updated View Revisions
2016-07-15 00:45 abma Description Updated View Revisions
2016-07-15 01:51 abma Note Added: 0016507
2016-07-15 23:11 hokomoko Assigned To => hokomoko
2016-07-15 23:11 hokomoko Status feedback => assigned
2016-07-16 18:25 hokomoko Changeset attached => spring develop 0354b349
2016-07-16 18:25 hokomoko Note Added: 0016512
2016-07-16 18:25 hokomoko Status assigned => resolved
2016-07-16 18:25 hokomoko Resolution open => fixed
+Issue History