| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0005484 | Spring engine | General | public | 2017-02-20 04:32 | 2017-06-11 13:57 | ||||
| Reporter | Google_Frog | ||||||||
| Assigned To | Kloot | ||||||||
| Priority | normal | Severity | crash | Reproducibility | have not tried | ||||
| Status | closed | Resolution | not fixable | ||||||
| Product Version | 103.0 +git | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0005484: 103.0.1-648-g5775975 game crashes | ||||||||
| Description | Here are the recent crashes with stacktraces that seem to be engine related. Start of game crashes: https://github.com/ZeroK-RTS/CrashReports/issues/162 https://github.com/ZeroK-RTS/CrashReports/issues/147 Not the start of the game: https://github.com/ZeroK-RTS/CrashReports/issues/161 Start of game but with fragment shader warnings. I've never seen these warnings before, are they new? The stacktraces look the same as the ordinary start of game crashes. https://github.com/ZeroK-RTS/CrashReports/issues/157 https://github.com/ZeroK-RTS/CrashReports/issues/156 https://github.com/ZeroK-RTS/CrashReports/issues/155 https://github.com/ZeroK-RTS/CrashReports/issues/146 https://github.com/ZeroK-RTS/CrashReports/issues/145 https://github.com/ZeroK-RTS/CrashReports/issues/144 https://github.com/ZeroK-RTS/CrashReports/issues/143 https://github.com/ZeroK-RTS/CrashReports/issues/142 https://github.com/ZeroK-RTS/CrashReports/issues/141 Failure to allocate memory: https://github.com/ZeroK-RTS/CrashReports/issues/152 | ||||||||
| Tags | No tags attached. | ||||||||
| Checked infolog.txt for Errors | |||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
Kloot (developer) 2017-02-20 13:23 Last edited: 2017-02-20 13:42 |
162 is an ATI crash (note the "ATI Mobility Radeon HD 4500 Series" is ten years old at this point and so are the drivers this user has installed): rts/Rendering/Models/3DModel.cpp:77 rts/Rendering/Models/3DModel.h:153 rts/Rendering/Models/IModelParser.cpp:343 rts/Rendering/Models/IModelParser.cpp:269 rts/Rendering/Models/IModelParser.cpp:235 rts/Sim/Objects/SolidObjectDef.cpp:75 rts/Sim/Units/Unit.cpp:307 rts/Sim/Units/UnitDef.h:58 rts/Lua/LuaSyncedCtrl.cpp:1235 147 appears to contain two crashes rolled into one, but only the first is somewhat intelligible: rts/lib/lua/src/lvm.cpp:326 rts/lib/lua/src/lobject.cpp:167 rts/lib/lua/src/lobject.cpp:211 rts/lib/lua/src/ldebug.cpp:259 rts/lib/lua/src/lapi.cpp:493 rts/lib/lua/src/lauxlib.cpp:84 rts/lib/lua/src/lauxlib.cpp:91 rts/Lua/LuaUnsyncedRead.cpp:1599 rts/System/Misc/SpringTime.cpp:158 rts/Lua/LuaUnsyncedRead.cpp:1580 rts/Lua/LuaUnsyncedRead.cpp:1899 161 is an ATI crash in glCallList (from an "AMD Radeon HD 7600 Series"): rts/Lua/LuaOpenGL.cpp:4144 rts/lib/lua/src/ldo.cpp:321 rts/lib/lua/src/lvm.cpp:613 rts/Lua/LuaShaders.cpp:535 rts/lib/lua/src/ldo.cpp:378 /opt/mxe/tmp-gcc/gcc-4.8.1.build/i686-w64-mingw32/libgcc/./gthr-default.h:628 rts/lib/lua/src/lapi.cpp:813 rts/lib/lua/src/ldo.cpp:119 rts/lib/lua/src/ldo.cpp:378 rts/lib/lua/src/ldo.cpp:465 rts/lib/lua/src/lapi.cpp:327 rts/lib/lua/src/lbaselib.cpp:378 rts/lib/lua/src/ldo.cpp:321 rts/lib/lua/src/lvm.cpp:613 rts/lib/lua/src/ldo.cpp:378 156+157 both end in the same place as 162: rts/Rendering/Models/3DModel.cpp:77 rts/Rendering/Models/3DModel.h:153 rts/Rendering/Models/3DModel.h:153 rts/Rendering/Models/IModelParser.cpp:343 rts/Rendering/Models/IModelParser.cpp:269 rts/Rendering/Models/IModelParser.cpp:235 rts/Sim/Objects/SolidObjectDef.cpp:75 rts/Lua/LuaOpenGLUtils.cpp:271 rts/Lua/LuaOpenGL.cpp:3199 155 is a useless trace 141-146 are all the same as 162 (and mostly from one user with an "ATI Mobility Radeon HD 4500 Series", there is also a single HD4300 report), model creation ending in a crash when generating display lists It's doubtful these ATI (Mobility Radeon HD 4xxx) issues are fixable in-engine, although for obvious reasons the COS framework should not even try to compile shaders on such hardware. |
|
Kloot (developer) 2017-06-11 13:57 |
ATI crashes have subsided with game/lobby-side measures, drivers are still terrible. 147 was memory corruption, fixed in various commits after g5775975. 152 was/is part of an ongoing effort. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-02-20 04:32 | Google_Frog | New Issue | |
| 2017-02-20 13:23 | Kloot | Note Added: 0017356 | |
| 2017-02-20 13:42 | Kloot | Note Edited: 0017356 | View Revisions |
| 2017-06-11 13:57 | Kloot | Assigned To | => Kloot |
| 2017-06-11 13:57 | Kloot | Status | new => closed |
| 2017-06-11 13:57 | Kloot | Resolution | open => not fixable |
| 2017-06-11 13:57 | Kloot | Note Added: 0017828 | |
| Issue History |