beam 100% cpu leads to disconnect
It has been reported that the beam process got in aloop, using 100% cpu. Erlide reported the backend as dead (probably because the heartbeat didn't come in time), but there was no message "please restart" because it is shown when the beam process itself is dead.
There are several issues here, will create tickets for each of them.
There are several issues here, will create tickets for each of them.
Leave a comment
on 2012-04-25 05:58 *
By Vlad Dumitrescu
Estimate changed from Small to Medium
Sum of child estimates changed from 4.0 to 6.0
Estimate changed from Small to Medium
Sum of child estimates changed from 4.0 to 6.0
on 2012-04-25 05:58 *
By Vlad Dumitrescu
Estimate changed from Medium to Large
Sum of child estimates changed from 6.0 to 12.0
Estimate changed from Medium to Large
Sum of child estimates changed from 6.0 to 12.0
on 2012-04-25 05:58 *
By Vlad Dumitrescu
Estimate changed from Large to None
Sum of child estimates changed from 16.0 to 7.0
Estimate changed from Large to None
Sum of child estimates changed from 16.0 to 7.0
on 2013-01-09 03:21 *
By Vlad Dumitrescu
Affected by xtext set to Yes
Milestone changed from deprecated because of xtext version to backlog
Affected by xtext set to Yes
Milestone changed from deprecated because of xtext version to backlog
on 2013-01-22 06:14 *
By Vlad Dumitrescu
Status changed from New to Test
Status changed from New to Test
on 2013-01-22 06:14 *
By Vlad Dumitrescu
Milestone changed from backlog to sprint #38
Milestone changed from backlog to sprint #38
on 2013-01-22 07:17 *
By Vlad Dumitrescu
Status changed from Test to Fixed
Status changed from Test to Fixed