Opened 13 years ago
Closed 9 years ago
#978 closed defect (worksforme)
Rare crash in Intel drivers in glvwprintf on Win7
Reported by: | gudo | Owned by: | |
---|---|---|---|
Priority: | Nice to Have | Milestone: | |
Component: | Core engine | Keywords: | crash crashlog windows |
Cc: | Patch: |
Description
Using SVN at r10318. Not sure what caused it, haven't been able to re-produce.
Attachments (3)
Change History (10)
by , 13 years ago
Attachment: | crashlog.txt added |
---|
comment:1 by , 13 years ago
Keywords: | crash crashlog → crash,crashlog |
---|
comment:2 by , 13 years ago
Seems like this is sometimes reproduceable when testing qBot via quickstart (see below for full list of arguments used) and manually placing buildings and tasking the militia to build and gather.
"D:\0ad\-dev\binaries\system\"pyrogenesis.exe -nosound -quickstart -autostart=cantabrian_highlands -autostart-random -mod "Cantabrian Highlands" -autostart-ai=1:qBot -autostart-ai=2:JuBot -autostart-players=2
Additional details: Sometimes crashlog throws errno 0, (see attached) and sometimes it throws:
(error while dumping stack: No stack frames found) errno = 42 (?) OS error = 487 (Attempt to access invalid address.)
comment:3 by , 13 years ago
The indication of your crash dumps is that the error is occurring in ig4icd32.dll, which is part of the Intel graphics drivers. Do you have the latest drivers, have you updated recently? I can't be sure about that until I can build that version of the game (to get the debug symbols).
comment:4 by , 12 years ago
Both dump files have call stacks starting:
ig4icd32.dll!07129e0a() [Frames below may be incorrect and/or missing, no symbols loaded for ig4icd32.dll] pyrogenesis.exe!glvwprintf(const wchar_t * fmt, char * args) Line 331 C++ pyrogenesis.exe!glwprintf(const wchar_t * fmt, ...) Line 347 + 0xf bytes C++ pyrogenesis.exe!CGUI::DrawText(SGUIText & Text, const CColor & DefaultColor, const CPos & pos, const float & z, const CRect & clipping) Line 972 + 0x14 bytes C++
In glvwprintf
, buf
is "520" in the first dump, "68" in the second. (Presumably this is drawing a resource counter or similar text.)
I have no idea why this could be failing, other than weird random driver bugs.
comment:5 by , 12 years ago
Summary: | Unhandled Execption on Win 7 64 bit → Rare crash in Intel drivers in glvwprintf on Win7 |
---|
#1018 had the same problem.
comment:6 by , 11 years ago
Keywords: | windows added |
---|
comment:7 by , 9 years ago
Milestone: | Backlog |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
crashlog.txt