backend stuck with 100% cpu, why?
This might be related to the "error 134" crashes.
Can we find out what happens?
- activate core dumps
- other?
Can we find out what happens?
- activate core dumps
- other?
Leave a comment
on 2012-04-25 04:33 *
By Vlad Dumitrescu
Priority changed from Normal (3) to High (2)
Priority changed from Normal (3) to High (2)
on 2012-04-25 04:40 *
By Vlad Dumitrescu
Assigned to set to Vlad Dumitrescu
Assigned to set to Vlad Dumitrescu
on 2012-04-25 07:58 *
By Vlad Dumitrescu
Estimate changed from Small to Medium
Sum of child estimates changed from 1.0 to 3.0
Estimate changed from Small to Medium
Sum of child estimates changed from 1.0 to 3.0
on 2012-04-25 08:55 *
By Vlad Dumitrescu
Shade ticket changed from 2528.0 to -none-
Shade ticket changed from 2528.0 to -none-
disconnected from shade ticket.
on 2013-01-09 04: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 07:15 *
By Vlad Dumitrescu
Status changed from New to Fixed
Status changed from New to Fixed
on 2013-01-22 07:15 *
By Vlad Dumitrescu
Milestone changed from backlog to sprint #38
Milestone changed from backlog to sprint #38