View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
ID | Project | Category | View Status | Date Submitted | Last Update |
0003733 | Doomseeker | [All Projects] Bug | public | 2020-01-19 16:13 | 2020-01-19 16:22 |
|
Reporter | WubTheCaptain | |
Assigned To | | |
Priority | none | Severity | major | Reproducibility | have not tried |
Status | new | Resolution | open | |
Platform | Microsoft | OS | Windows | OS Version | XP/Vista/7 |
Product Version | 1.3 | |
Target Version | | Fixed in Version | | |
|
Summary | 0003733: Auto-updates may fire late after other buggy threads / functions have initiated and crashed the program |
Description | Since auto-updates happen after IP2C initialization and refreshing thread initialization (& more), if there are bugs causing crashes in those threads (such as 0003728 or 0003395) or functions, the auto-update may fail and not have enough time to auto-update Doomseeker before those threads crash Doomseeker. Needless to say this is pretty terrible UX on Windows and has likely bitten us hard once already, and is very tightly integrated to Doomseeker's main program. |
Steps To Reproduce | See src/core/main.cpp.
'https://bitbucket.org/Doomseeker/doomseeker/src/1.3/src/core/main.cpp#lines-176:184,209:229,237:251 [^]' |
Additional Information | 0003728:0021102, 0003728:0021106 |
|
Attached Files | |
|