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

Repeating crashes during combat processing at last nodes #16

Closed
stackhanovets opened this issue Nov 30, 2017 · 10 comments
Closed

Repeating crashes during combat processing at last nodes #16

stackhanovets opened this issue Nov 30, 2017 · 10 comments
Labels
module:combat

Comments

@stackhanovets
Copy link

stackhanovets commented Nov 30, 2017 •
edited
Loading

Few maps were tested, the interruptions had happened from time to time and had thrown similar tracebacks.

Log:

[date time] Expeditions sent: 3 / received: 2
[date time] Combat done: 4 / attempted: 6
[date time] Resupplies: 6 || Repairs: 5 || Buckets: 5
[date time] Recoveries done: 0
[log] App.focus:  [Chrome]
[date time] At side menu
[date time] Going home.
[log] CLICK on L(78,367)@S(0)[0,0 resolution] (553 msec)
[date time] At home
[date time] At home
[date time] Navigating to combat screen.
[log] CLICK on L(205,404)@S(0)[0,0 resolution] (555 msec)
[log] CLICK on L(209,337)@S(0)[0,0 resolution] (572 msec)
[log] CLICK on L(717,555)@S(0)[0,0 resolution] (529 msec)
[date time] Begin resupplying LBAS groups.
[log] CLICK on L(196,507)@S(0)[0,0 resolution] (559 msec)
[date time] Resupplying LBAS group 1.
{'medium': False, 'high': False}
[date time] LBAS group switched to sortie mode.
[log] CLICK on L(261,505)@S(0)[0,0 resolution] (561 msec)
[log] CLICK on L(632,386)@S(0)[0,0 resolution] (531 msec)
[log] CLICK on L(731,559)@S(0)[0,0 resolution] (555 msec)
[log] CLICK on L(427,227)@S(0)[0,0 resolution] (546 msec)
{'medium': False, 'high': False}
[log] CLICK on L(655,552)@S(0)[0,0 resolution] (605 msec)
[date time] Assign LBAS groups to nodes.
[date time] Assigning nodes for LBAS group 1.
[log] CLICK on L(658,173)@S(0)[0,0 resolution] (634 msec)
[date time] Fleet at Node Q
[date time] Engaging the enemy in diamond formation.
[log] CLICK on L(738,295)@S(0)[0,0 resolution] (657 msec)
[date time] Continuing sortie.
[log] CLICK on L(313,332)@S(0)[0,0 resolution] (566 msec)
[date time] Fleet at Node K
[date time] Engaging the enemy in line ahead formation.
[log] CLICK on L(434,295)@S(0)[0,0 resolution] (559 msec)
[date time] Continuing sortie.
[log] CLICK on L(315,354)@S(0)[0,0 resolution] (589 msec)
[date time] Fleet at Node L
[date time] Engaging the enemy in line ahead formation.
[log] CLICK on L(468,293)@S(0)[0,0 resolution] (634 msec)
[date time] Continuing sortie.
[log] CLICK on L(313,341)@S(0)[0,0 resolution] (585 msec)
[date time] Fleet at Node M
[date time] Engaging the enemy in diamond formation.
[log] CLICK on L(692,292)@S(0)[0,0 resolution] (577 msec)
[date time] Continuing sortie.
[log] CLICK on L(300,342)@S(0)[0,0 resolution] (594 msec)
[date time] Fleet at Node P(backup)
[date time] Engaging the enemy in line ahead formation.
[log] CLICK on L(470,299)@S(0)[0,0 resolution] (658 msec)
[date time] Commencing night battle.
[log] CLICK on L(520,332)@S(0)[0,0 resolution] (572 msec)
[log] App.focus:  [Chrome]
[date time] Irrecoverable crash
FindFailed: next.png: (resolution) seen at (746, 528) with 1.00 in R[718,502 resolution]@S(0) E:Y, T:1.0
  Line 2755, in file Region.java

[error] script [ .../kcauto-kai/kcauto-kai.sikuli ] stopped with error in line 76
[error] FindFailed ( next.png: (resolution) seen at (746, 528) with 1.00 in R[718,502 resolution]@S(0) E:Y, T:1.0 )
[error] --- Traceback --- error source first
line: module ( function ) statement 
328: combat (  _run_combat_logic )     self.regions['lower_right_corner'].wait('next.png', 30)
116: combat (  combat_logic_wrapper )     self._run_combat_logic()
310: main (  run_combat_cycle )     if self.modules['combat'].combat_logic_wrapper():
64: main (  <module> )     kcauto_kai.run_combat_cycle()
[error] --- Traceback --- end --------------

Cfg:

[Combat]
Enabled: True
Map: E-2
FleetMode: striking
CombatNodes: 5
NodeSelects: 
RetreatLimit: heavy
RepairLimit: moderate
RepairTimeLimit: 0100
LBASGroups: 1
LBASGroup1Nodes: P,P
LBASGroup2Nodes: 
LBASGroup3Nodes: 
MiscOptions: CheckFatigue,PortCheck
@mrmin123
Copy link
Collaborator

Stack traces aren't enough here... what screen did it crash on? What was the game doing? More details are needed to debug. I haven't had issues with combat resolving on my machines.

@stackhanovets
Copy link
Author

I've just caught it again with the same cfg:

combat_crash

So I've also caught the repair module crash:
repair_crash

[date time] Sortie complete. Encountered 3 combat nodes (nodes Q, K, L).
reset expedition fleets
[date time] At home
[date time] At home
[date time] Navigating to repair screen.
[log] CLICK on L(126,470)@S(0)[0,0 resolution] (540 msec)
[date time] Begin repairing fleets.
[log] CLICK on L(299,270)@S(0)[0,0 resolution] (574 msec)
[date time] Picking damaged ship from combat fleet(s) to repair.
[log] CLICK on L(580,280)@S(0)[0,0 resolution] (540 msec)
[date time] Got invalid timer (3855)... trying again!
[date time] Got valid timer (time)!
[log] CLICK on L(755,397)@S(0)[0,0 resolution] (543 msec)
[log] CLICK on L(630,560)@S(0)[0,0 resolution] (560 msec)
[log] CLICK on L(510,508)@S(0)[0,0 resolution] (543 msec)
[log] CLICK on L(266,357)@S(0)[0,0 resolution] (616 msec)
[date time] Picking damaged ship from combat fleet(s) to repair.
[log] CLICK on L(606,251)@S(0)[0,0 resolution] (574 msec)
[date time] Got invalid timer (05800)... trying again!
[date time] Got valid timer (time)!
[log] CLICK on L(714,403)@S(0)[0,0 resolution] (532 msec)
[log] CLICK on L(625,541)@S(0)[0,0 resolution] (569 msec)
[log] CLICK on L(537,512)@S(0)[0,0 resolution] (572 msec)
[log] App.focus:  [Chrome]
[date time] Irrecoverable crash
FindFailed: dock_empty.png: (resolution) seen at (178, 333) with 1.00 in R[5,112 resolution]@S(0) E:Y, T:1.0
  Line 2754, in file Region.java

[error] script [ /home/user/Sikuli/kcauto-kai/kcauto-kai.sikuli ] stopped with error in line 76
[error] FindFailed ( dock_empty.png: (resolution) seen at (178, 333) with 1.00 in R[5,112 resolution]@S(0) E:Y, T:1.0 )
[error] --- Traceback --- error source first
line: module ( function ) statement 
110: repair (  _conduct_repair )     self.kc_region.wait('dock_empty.png')
75: repair (  repair_fleets )     self._conduct_repair()
359: main (  run_repair_cycle )     self.modules['repair'].repair_fleets()
66: main (  <module> )     kcauto_kai.run_repair_cycle()
[error] --- Traceback --- end --------------

CentOS 7, yum update'd yesterday. 4 cores, 8G RAM, openJDK build 1.8.0_151-b12.

$ free
              total        used        free      shared  buff/cache   available
Mem:        7994076     6647176      226348       46732     1120552      927396
Swap:       8258556        1480     8257076

@mrmin123 mrmin123 mentioned this issue Dec 3, 2017
Closed
@stackhanovets
Copy link
Author

Just pulled it again and caught the crash at the same screen:

[date time] Initializing config module
[date time] Reading config
[date time] Validating config
[date time] Starting kancolle-auto!
[log] App.focus:  [Chrome]
[date time] At home
[date time] At home
[date time] Refreshing home.
[log] CLICK on L(129,475)@S(0)[0,0 resolution] (666 msec)
[log] CLICK on L(78,364)@S(0)[0,0 resolution] (726 msec)
[log] App.focus:  [Chrome]
[date time] At home
[date time] At home
[date time] At home
[date time] Navigating to expedition screen.
[log] CLICK on L(207,400)@S(0)[0,0 resolution] (616 msec)
[log] CLICK on L(676,340)@S(0)[0,0 resolution] (677 msec)
[date time] Sortieing fleet 3 to expedition 9998
[log] CLICK on L(513,541)@S(0)[0,0 resolution] (634 msec)
[log] CLICK on L(224,291)@S(0)[0,0 resolution] (700 msec)
[log] CLICK on L(655,550)@S(0)[0,0 resolution] (570 msec)
[log] CLICK on L(427,222)@S(0)[0,0 resolution] (624 msec)
[log] CLICK on L(673,562)@S(0)[0,0 resolution] (588 msec)
[date time] Fleet 3 sortied. Expected return time: date time
[date time] Sortieing fleet 4 to expedition 9999
[log] CLICK on L(263,324)@S(0)[0,0 resolution] (573 msec)
[log] CLICK on L(708,552)@S(0)[0,0 resolution] (682 msec)
[log] CLICK on L(457,228)@S(0)[0,0 resolution] (629 msec)
[log] CLICK on L(597,563)@S(0)[0,0 resolution] (629 msec)
[date time] Fleet 4 sortied. Expected return time: date time
[log] App.focus:  [Chrome]
[date time] At side menu
[date time] Going home.
[log] CLICK on L(27,263)@S(0)[0,0 resolution] (564 msec)
[log] CLICK on L(81,368)@S(0)[0,0 resolution] (657 msec)
[date time] At home
[date time] At home
[date time] Navigating to combat screen.
[log] CLICK on L(204,365)@S(0)[0,0 resolution] (593 msec)
[log] CLICK on L(222,300)@S(0)[0,0 resolution] (724 msec)
[log] CLICK on L(728,560)@S(0)[0,0 resolution] (595 msec)
[date time] Begin resupplying LBAS groups.
[log] CLICK on L(205,510)@S(0)[0,0 resolution] (623 msec)
[date time] Resupplying LBAS group 1.
[date time] Resupplying LBAS group 2.
[log] CLICK on L(693,234)@S(0)[0,0 resolution] (631 msec)
[log] CLICK on L(235,496)@S(0)[0,0 resolution] (620 msec)
[log] CLICK on L(662,489)@S(0)[0,0 resolution] (557 msec)
[log] CLICK on L(719,560)@S(0)[0,0 resolution] (716 msec)
[date time] Fleet 1 damage counts: 0 heavy / 0 moderate / 1 minor
[log] CLICK on L(397,230)@S(0)[0,0 resolution] (699 msec)
[date time] Fleet 2 damage counts: 0 heavy / 0 moderate / 1 minor
[log] CLICK on L(369,223)@S(0)[0,0 resolution] (618 msec)
[log] CLICK on L(635,543)@S(0)[0,0 resolution] (760 msec)
[date time] Assign LBAS groups to nodes.
[date time] Assigning nodes for LBAS group 1.
[date time] Fleet at Node #1
[date time] Engaging the enemy in combinedfleet 1 formation.
[log] CLICK on L(488,285)@S(0)[0,0 resolution] (672 msec)
[date time] Fleet 1 damage counts: 0 heavy / 0 moderate / 1 minor
[date time] Fleet 2 damage counts: 0 heavy / 0 moderate / 1 minor
[date time] Continuing sortie.
[log] CLICK on L(303,344)@S(0)[0,0 resolution] (753 msec)
[date time] Fleet at Node #2
[date time] Engaging the enemy in combinedfleet 4 formation.
[log] CLICK on L(664,422)@S(0)[0,0 resolution] (558 msec)
[date time] Fleet 1 damage counts: 0 heavy / 0 moderate / 1 minor
[date time] Fleet 2 damage counts: 0 heavy / 0 moderate / 1 minor
[date time] Continuing sortie.
[log] CLICK on L(312,342)@S(0)[0,0 resolution] (617 msec)
[date time] Fleet at Node #3
[date time] Engaging the enemy in combinedfleet 3 formation.
[log] CLICK on L(538,418)@S(0)[0,0 resolution] (700 msec)
[date time] Fleet 1 damage counts: 0 heavy / 0 moderate / 1 minor
[date time] Fleet 2 damage counts: 0 heavy / 0 moderate / 1 minor
[date time] Continuing sortie.
[log] CLICK on L(300,339)@S(0)[0,0 resolution] (723 msec)
[date time] Fleet at Node #4
[date time] Engaging the enemy in combinedfleet 1 formation.
[log] CLICK on L(543,290)@S(0)[0,0 resolution] (722 msec)
[date time] Fleet 1 damage counts: 0 heavy / 0 moderate / 1 minor
[date time] Fleet 2 damage counts: 0 heavy / 0 moderate / 1 minor
[date time] Continuing sortie.
[log] CLICK on L(296,336)@S(0)[0,0 resolution] (747 msec)
[date time] Fleet at Node #5
[date time] Engaging the enemy in combinedfleet 4 formation.
[log] CLICK on L(639,426)@S(0)[0,0 resolution] (645 msec)
[date time] Fleet 1 damage counts: 0 heavy / 0 moderate / 1 minor
[date time] Fleet 2 damage counts: 0 heavy / 0 moderate / 1 minor
[date time] Continuing sortie.
[log] CLICK on L(301,349)@S(0)[0,0 resolution] (608 msec)
[date time] Fleet at Node #6
[date time] Engaging the enemy in combinedfleet 3 formation.
[log] CLICK on L(481,423)@S(0)[0,0 resolution] (628 msec)
[date time] Fleet 1 damage counts: 0 heavy / 0 moderate / 1 minor
[date time] Fleet 2 damage counts: 0 heavy / 0 moderate / 1 minor
[date time] Continuing sortie.
[log] CLICK on L(290,346)@S(0)[0,0 resolution] (586 msec)
[date time] Fleet at Node #7
[date time] Engaging the enemy in combinedfleet 4 formation.
[log] CLICK on L(649,415)@S(0)[0,0 resolution] (730 msec)
[date time] Commencing night battle.
[log] CLICK on L(501,352)@S(0)[0,0 resolution] (654 msec)
[date time] FindFailed error occurred; attempting basic recovery.
[log] App.focus:  [Chrome]
[date time] Irrecoverable crash
FindFailed: next.png: (resolution) seen at (746, 528) with 0.98 in R[718,502 resolution]@S(0) E:Y, T:1.0
  Line 2755, in file Region.java

[error] script [ .../kcauto-kai/kcauto-kai.sikuli ] stopped with error in line 76
[error] FindFailed ( next.png: (resolution) seen at (746, 528) with 0.98 in R[718,502 resolution]@S(0) E:Y, T:1.0 )
[error] --- Traceback --- error source first
line: module ( function ) statement 
334: combat (  _run_combat_logic )     self.regions['lower_right_corner'].wait('next.png', 30)
113: combat (  combat_logic_wrapper )     self._run_combat_logic()
311: main (  run_combat_cycle )     if self.modules['combat'].combat_logic_wrapper():
64: main (  <module> )     kcauto_kai.run_combat_cycle()
[error] --- Traceback --- end --------------

Any ideas?

@mrmin123
Copy link
Collaborator

mrmin123 commented Dec 7, 2017

It's still happening on the screen that shows the sortie score (like in this comment)?

You're on the latest version?

@stackhanovets
Copy link
Author

The last time it has happened just after night battle. The screen had closed by blue semiblocks, the fleet information had first appeared before score rank screen, the script had tiggered and crashed. There were only ~200 ms while the fleet was on screen top.

$ git log | head
commit 2ddf4bb11120556e5fd726ba6c5b4fc264549d11
Merge: 388fe0a 113edbe
Author: Minyoung Choi <mrmin123@users.noreply.github.com>
Date:   Wed Dec 6 21:06:14 2017 -0800

    Merge pull request #31 from mrmin123/staging
    
    0.2.3 to master

commit 113edbedb33bbdadba8b192efe5e38120e52acfb

@mrmin123
Copy link
Collaborator

mrmin123 commented Dec 7, 2017 •
edited
Loading

blue semiblocks

What is this? What 'screen' did it close?

IIRC the fleet information flashes briefly on-screen, and then the score screen is overlayed on top of it, and then the next.png image shows up in the lower left corner (the part that the script is waiting for).

@stackhanovets
Copy link
Author

Fine, let me reproduce it.

kancolle 2017 fall e-4 hard 1st boss last dance strait prin mp4_20171208_011905 330
kancolle 2017 fall e-4 hard 1st boss last dance strait prin mp4_20171208_012004 730

SCRIPT CRASHES!11

kancolle 2017 fall e-4 hard 1st boss last dance strait prin mp4_20171208_012138 053
kancolle 2017 fall e-4 hard 1st boss last dance strait prin mp4_20171208_012245 504
kancolle 2017 fall e-4 hard 1st boss last dance strait prin mp4_20171208_012352 487

@mrmin123
Copy link
Collaborator

mrmin123 commented Dec 7, 2017 •
edited
Loading

I have no idea what might be causing this on your end. A possible fix is to change L511-512:

            elif (self.kc_region.exists('next.png')
                    or self.kc_region.exists('next_alt.png')):

to

            elif (self.regions['lower_right_corner'].exists('next.png')
                    or self.regions['lower_right_corner'].exists('next_alt.png')):

(I should probably make this change anyways for optimization purposes)

@mrmin123
Copy link
Collaborator

mrmin123 commented Dec 9, 2017

@stackhanovets the above change was pushed to master as of 0.2.4; has the issue been repeated since?

@stackhanovets
Copy link
Author

@mrmin123 Good. I've tested normal, combined and strike force fleet - no more crashes have been occurred. However, in some times the script had stuck confusing minor damage sign on sortie start screen wiith fatique icon or during boss quote screen processing:

1

2

[Combat]
Enabled: True
Engine: legacy
Map: E-3
FleetMode: ctf
CombatNodes: 7
NodeSelects: 
Formations: 1:combinedfleet_1,2:combinedfleet_4,3:combinedfleet_3,4:combinedfleet_1,5:combinedfleet_4,6:combinedfleet_3,7:combinedfleet_4
NightBattles: 7:True
RetreatLimit: heavy
RepairLimit: moderate
RepairTimeLimit: 0100
LBASGroups: 1,2,3
LBASGroup1Nodes: G,G
LBASGroup2Nodes: 
LBASGroup3Nodes: G,G
MiscOptions: PortCheck

So the topic is solved.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
module:combat
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mrmin123 @stackhanovets