wine-20050930 Warblade install error

[Sebastien Fievet]

Hi all,

I have the following error when trying to install Warblade (old fashioned
shoot'em up) :

WINEDLLOVERRIDES="comctl32=n" wine Download/Warblade_12E_full.exe
err:heap:HEAP_ValidateInUseArena Heap 0x41a20000: in-use arena 0x41a2c408 next
block has PREV_FREE flag

I found various messages related to heap error by browsing the mailing-lists
archives, but no patch neither solution so far...

Any clue on how to fix this?

Regards, Sebastien.

[Marcus Meissner]

On Sat, Oct 01, 2005 at 02:55:01PM +0200, Sebastien Fievet wrote:
> Hi all,
>
> I have the following error when trying to install Warblade (old fashioned
> shoot'em up) :
>
> WINEDLLOVERRIDES="comctl32=n" wine Download/Warblade_12E_full.exe
> err:heap:HEAP_ValidateInUseArena Heap 0x41a20000: in-use arena 0x41a2c408 next
> block has PREV_FREE flag
>
> I found various messages related to heap error by browsing the mailing-lists
> archives, but no patch neither solution so far...
>
> Any clue on how to fix this?

You need to find out the actual heap corruption.

Please run with

WINEDEBUG=+relay,+heap WINEDLLOVERRIDES="comctl32=n" wine Download/Warblade_12E_full.exe >logfile 2>&1

And check logfile at the place of the actual heap corruption.

Ciao, Marcus

[Sebastien Fievet]

> You need to find out the actual heap corruption.
>
> Please run with
>
> WINEDEBUG=+relay,+heap WINEDLLOVERRIDES="comctl32=n" wine
> Download/Warblade_12E_full.exe >logfile 2>&1
>
> And check logfile at the place of the actual heap corruption.
>
> Ciao, Marcus

Hello Marcus,

i ran that command you gave me, and wine dumped a 171M log file... :-(
It's fairly large considering it crashes right before starting to install the
game.
I don't know how a heap corruption look like... Below are the last log files
lines. Tell me if it's meaningful or if you need something else.

[...almost end of file]
0009:Ret  kernel32.TlsFree() retval=00000001 ret=40a03c4b
0009:Ret  PE DLL (proc=0x40a12640,module=0x409c0000
L"winex11.drv",reason=PROCESS_DETACH,res=0x1) retval=1 0009:Call PE DLL
(proc=0x40798880,module=0x40760000 L"gdi32.dll",reason=PROCESS_DETACH,res=0x1)
0009:Ret  PE DLL (proc=0x40798880,module=0x40760000
L"gdi32.dll",reason=PROCESS_DETACH,res=0x1) retval=1 0009:Call PE DLL
(proc=0x407e7680,module=0x407d0000
L"advapi32.dll",reason=PROCESS_DETACH,res=0x1) 0009:Ret  PE DLL
(proc=0x407e7680,module=0x407d0000
L"advapi32.dll",reason=PROCESS_DETACH,res=0x1) retval=1 0009:Call PE DLL
(proc=0x40494220,module=0x40430000
L"kernel32.dll",reason=PROCESS_DETACH,res=0x1) 0009:Call
ntdll.RtlEnterCriticalSection(404fb340) ret=404747bc 0009:Ret
ntdll.RtlEnterCriticalSection() retval=00000000 ret=404747bc 0009:Call
ntdll.RtlLeaveCriticalSection(404fb340) ret=404747c7 0009:Ret
ntdll.RtlLeaveCriticalSection() retval=00000000 ret=404747c7 0009:Ret  PE DLL
(proc=0x40494220,module=0x40430000
L"kernel32.dll",reason=PROCESS_DETACH,res=0x1) retval=1 0009:Call PE DLL
(proc=0x401a9d00,module=0x40170000 L"ntdll.dll",reason=PROCESS_DETACH,res=0x1)
0009:Ret  PE DLL (proc=0x401a9d00,module=0x40170000
L"ntdll.dll",reason=PROCESS_DETACH,res=0x1) retval=1 0009:Ret
ntdll.LdrShutdownProcess() retval=00000000 ret=4046ed78 0009:Call
ntdll.NtTerminateProcess(ffffffff,00000001) ret=4046ed80 0009:Call
ntdll.RtlEnterCriticalSection(40323b00) ret=404770e2

[...end of file]
trace:heap:RtlFreeHeap (0x40300000,00000002,0x40323b20): returning TRUE
0009:Ret  ntdll.RtlDeleteCriticalSection() retval=00000000 ret=404771db
0009:Call ntdll.RtlFreeHeap(40300000,00000000,40323b00) ret=4045097d
trace:heap:RtlFreeHeap (0x40300000,00000002,0x40323b00): returning TRUE
0009:Ret  ntdll.RtlFreeHeap() retval=00000001 ret=4045097d
0009:Call ntdll.RtlDeleteCriticalSection(40323ab8) ret=404771db
trace:heap:RtlFreeHeap (0x40300000,00000002,0x40323ad8): returning TRUE
0009:Ret  ntdll.RtlDeleteCriticalSection() retval=00000000 ret=404771db
0009:Call ntdll.RtlFreeHeap(40300000,00000000,40323ab8) ret=4045097d
trace:heap:RtlFreeHeap (0x40300000,00000002,0x40323ab8): returning TRUE
0009:Ret  ntdll.RtlFreeHeap() retval=00000001 ret=4045097d
0009:Call ntdll.RtlEnterCriticalSection(40300978) ret=404770e2
0009:Ret  ntdll.RtlEnterCriticalSection() retval=00000000 ret=404770e2
0009:Call ntdll.RtlLeaveCriticalSection(40300978) ret=4047717a
0009:Ret  ntdll.RtlLeaveCriticalSection() retval=00000000 ret=4047717a
0009:Call ntdll.RtlAllocateHeap(40300000,00000000,00000018) ret=4045093d
trace:heap:RtlAllocateHeap (0x40300000,00000002,00000018): returning 0x40323ab8
0009:Ret  ntdll.RtlAllocateHeap() retval=40323ab8 ret=4045093d
0009:Call ntdll.RtlInitializeCriticalSection(40323ab8) ret=4047784b
trace:heap:RtlAllocateHeap (0x40300000,00000002,00000020): returning 0x40323ad8
0009:Ret  ntdll.RtlInitializeCriticalSection() retval=00000000 ret=4047784b
0009:Call ntdll.RtlEnterCriticalSection(40323ab8) ret=404770e2
0009:Ret  ntdll.RtlEnterCriticalSection() retval=00000000 ret=404770e2
0009:Call ntdll.RtlLeaveCriticalSection(40323ab8) ret=4047717a
0009:Ret  ntdll.RtlLeaveCriticalSection() retval=00000000 ret=4047717a
0009:Call ntdll.RtlEnterCriticalSection(40300280) ret=404770e2
0009:Ret  ntdll.RtlEnterCriticalSection() retval=00000000 ret=404770e2
0009:Call ntdll.RtlLeaveCriticalSection(40300280) ret=4047717a

Regards, Seb

[Marcus Meissner]

On Tue, Oct 04, 2005 at 08:43:08AM +0200, Sebastien Fievet wrote:
> > You need to find out the actual heap corruption.
> >
> > Please run with
> >
> > WINEDEBUG=+relay,+heap WINEDLLOVERRIDES="comctl32=n" wine
> > Download/Warblade_12E_full.exe >logfile 2>&1
> >
> > And check logfile at the place of the actual heap corruption.
> >
> > Ciao, Marcus
>
> Hello Marcus,
>
> i ran that command you gave me, and wine dumped a 171M log file... :-(
> It's fairly large considering it crashes right before starting to install the
> game.
> I don't know how a heap corruption look like... Below are the last log files
> lines. Tell me if it's meaningful or if you need something else.

Look/grep for "err:heap" in the output.

There should be a large dump of heap entries right before or after it. We
mostly need the "relay" traces before that, 500 lines or so.

Ciao, Marcus

[Sebastien Fievet]

On Tue, 4 Oct 2005 08:50:07 +0200
Marcus Meissner  wrote:
> Look/grep for "err:heap" in the output.
>
> There should be a large dump of heap entries right before or after it. We
> mostly need the "relay" traces before that, 500 lines or so.
>
> Ciao, Marcus

Hi Marcus,

i sent the errors log files as an attachement to you only.
'Didn't know how to deal with it in the maling-list scope...

Regards, Seb.

[Jesse Allen]

On 10/4/05, Sebastien Fievet  wrote:
> On Tue, 4 Oct 2005 08:50:07 +0200
> Marcus Meissner  wrote:
> > Look/grep for "err:heap" in the output.
> >
> > There should be a large dump of heap entries right before or after it. We
> > mostly need the "relay" traces before that, 500 lines or so.
> >
> > Ciao, Marcus
>
> Hi Marcus,
>
> i sent the errors log files as an attachement to you only.
> 'Didn't know how to deal with it in the maling-list scope...
>
> Regards, Seb.

Best thing to do if you want everyone to see is to post it on a
webpage and give a link in the message =)  I something forget to do
that, and my messege gets dropped, so it is a good way to go.