View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018944 | MMW 5 | General | public | 2022-03-25 02:35 | 2022-04-24 12:05 |
| Reporter | barrym | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Platform | Windows | OS | - | OS Version | 10 |
| Product Version | 5.0.3 | ||||
| Target Version | 5.0.3 | Fixed in Version | 5.0.3 | ||
| Summary | 0018944: Something in MM5 debug version, or crash monitoring ,or crash handling is too heavy, or is looping. | ||||
| Description | Something in MM5 debug version, or crash monitoring ,or crash handling is too heavy, or is looping. I am running 2611. The last few MM5 crashes that I have had have left my PC in an unstable state. MM5 sits there consuming CPU at 18% + ... constantly It does not appear to stop ... ie. it runs for many minutes, until I kill it with the Windows Task Manager. It does not stop if I close MM5. It does not stop until I kill all of the MM5 processes. It is not logging anything to the DebugView monitor. What is causing this? Will It go away if I stop installing Debug versions? | ||||
| Steps To Reproduce | 1) run MM5 2611 debug edition 2) Trigger crash as described in Mantis 0018943 ... ie. try to cust and paste between playlists 3) ==> Crash. ... type in a description, and allow dump to be sent to Ventis 4) Press Continue button, and then close MM5 using the close control at top right of MM window 5) If am experience a 18% CPU loop at this point | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2615 | ||||
|
|
Already tracked as item 13) here: 0017654:0063928 i.e. can be trigered just by using menu Help > Debug > Send logs Needs to be fixed for 5.0.3 IMO MM5 should either self-restart and kill the leftovers -- or somehow gracefully go from this "locked" situation after the raised exception/crash. |
|
|
The issue is no longer happening in 2615 (after recent Petr's changes to Eureka handling). i.e. sending logs work fine and MM5 continues to work normally after submitting the log, testing both menu > Help > Debug > Send logs and submitted log 87990000 in case of issue 0018989 |
|
|
Verified 2616 Not observing issue anymore. |
