View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0021636 | MMW 5 | Other | public | 2025-06-10 14:01 | 2025-06-10 21:08 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | crash | Reproducibility | sometimes |
| Status | feedback | Resolution | open | ||
| Product Version | 2024.2 | ||||
| Target Version | 2024.2 | ||||
| Summary | 0021636: Crash while running in the background (E75F5AD9) | ||||
| Description | MMW build 3157 was running (not playing) in the background and the following crash occurred: E75F5AD9 (note: MMW had been running for about 12+ hours and the PC had gone to sleep, though I'm not sure whether going to sleep was related to the crash or not). After the crashlog was sent, the app was non-responsive and then crashlog E75F0000 occurred. The app had to be force-closed. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Yes, this was UI freeze detection after PC sleep... but there was a lot of non-MM related debug lines like 60538.204s - PID:47364 - [AC]:_tick 1749563817 s 1 u 1 f 0 avRAM:_7 % CPU:_73 % 60548.204s - PID:47364 - [AC]:_tick 1749563827 s 1 u 1 f 0 avRAM:_7 % CPU:_67 % 60585.768s - PID:3732 - [Default][TRACE][CEpPDFCreateEx::MemoryToPDF][CEpPDFCreateEx.cpp:155] in_pDstPath = C:\Users\russe\AppData\Local\Temp\dct1E60.tmp 60585.784s - PID:3732 - C:\Program Files (x86)\Epson Software\Scan OCR Cmponent Pro\DCP\FFMT\Eppdf2.dll Like it was scanning screen to PDF? So it looks like another sw/apps overloaded the PC and it could somehow result in the UI freeze detection ? |
|
|
Also I see that there was WM_POWERBROADCAST message with PBT_POWERSETTINGCHANGE and then enumeration of displays and desktop switching... Assigned to Petr to analyze the log too (whether he can see something there) as it relates to his code in browser process (as reaction on PBT_POWERSETTINGCHANGE) |
