| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0002132 | Frama-C | Plug-in > wp | public | 2015-06-11 02:25 | 2016-06-21 14:08 | ||||
| Reporter | gaggarwal | ||||||||
| Assigned To | correnson | ||||||||
| Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
| Status | closed | Resolution | fixed | ||||||
| Product Version | Frama-C Neon-20140301 | ||||||||
| Target Version | Fixed in Version | Frama-C Aluminium | |||||||
| Summary | 0002132: Under windows, many times, Frama-c wp process doesn't kill alt-ergo process before finishing | ||||||||
| Description | On Windows system, Frama-c wp process finished without finishing all the alt-ergo processes it created, because of this in few mins, my system starts thrashing because these lying around alt-ergo processes take up all the CPU time. If I run the test with frama-c wp + why3, why3 finishes all the alt-ergo processes before finishing. Is there an option, that should be used to make sure alt-ergo processes are finished with frama-c process? | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files |
| ||||||||
 Relationships |
 Notes |
|
| There are no notes attached to this issue. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-06-11 02:25 | gaggarwal | New Issue | |
| 2015-06-11 02:25 | gaggarwal | Status | new => assigned |
| 2015-06-11 02:25 | gaggarwal | Assigned To | => correnson |
| 2015-06-29 16:35 | correnson | Status | assigned => acknowledged |
| 2015-09-02 10:06 | correnson | Relationship added | related to 0002154 |
| 2015-11-25 15:40 | correnson | Status | acknowledged => resolved |
| 2015-11-25 15:40 | correnson | Fixed in Version | => Frama-C Aluminium |
| 2015-11-25 15:40 | correnson | Resolution | open => fixed |
| 2016-06-21 14:08 | signoles | Status | resolved => closed |
| Issue History |