Ticket #978 (new defect)

Opened 20 months ago

Last modified 18 months ago

Rare crash in Intel drivers in glvwprintf on Win7

Reported by: gudo Owned by:
Priority: Nice to Have Milestone: Backlog
Component: Core engine Keywords: crash,crashlog
Cc:

Description

Using SVN at r10318. Not sure what caused it, haven't been able to re-produce.

Attachments

crashlog.txt (15.0 KB) - added by gudo 20 months ago.
crashlog.txt
crashlog.dmp (46.8 KB) - added by gudo 20 months ago.
crashlog.dmp
crashlog.2.dmp (45.4 KB) - added by gudo 20 months ago.
crashlog.dmp

Change History

Changed 20 months ago by gudo

crashlog.txt

Changed 20 months ago by gudo

crashlog.dmp

comment:1 Changed 20 months ago by gudo

  • Keywords crash,crashlog added; crash crashlog removed

Changed 20 months ago by gudo

crashlog.dmp

comment:2 Changed 20 months ago by gudo

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 Changed 20 months ago by historic_bruno

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 Changed 18 months ago by Philip

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 Changed 18 months ago by Philip

  • Summary changed from Unhandled Execption on Win 7 64 bit to Rare crash in Intel drivers in glvwprintf on Win7

#1018 had the same problem.

Note: See TracTickets for help on using tickets.