HEADER_WindowProc unknown msg ?

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
walt

HEADER_WindowProc unknown msg ?

Post by walt »

I had an app running happily for over an hour, fetching realtime quotes
for foreign currencies, when it suddenly encountered "a serious problem"
i.e. a crash, and had to close. This is the error message from the
command line:

err:header:HEADER_WindowProc unknown msg 1264 wp=33f988 lp=0033f9e4

AFAIK there was nothing special happening at the time, and I wasn't
doing anything to the program.

Any ideas what happened?
Top
austin987
Wine Developer
Wine Developer
Posts: 2383
Joined: Fri Feb 22, 2008 8:19 pm

HEADER_WindowProc unknown msg ?

Post by austin987 »

On Tue, Jun 9, 2009 at 10:57 AM, walt<[email protected]> wrote:
I had an app running happily for over an hour, fetching realtime quotes
for foreign currencies, when it suddenly encountered "a serious problem"
i.e. a crash, and had to close.  This is the error message from the
command line:

err:header:HEADER_WindowProc unknown msg 1264 wp=33f988 lp=0033f9e4

AFAIK there was nothing special happening at the time, and I wasn't
doing anything to the program.

Any ideas what happened?



Was there more in the terminal?

--
-Austin
Top
walt

HEADER_WindowProc unknown msg ?

Post by walt »

On Tue, 9 Jun 2009, Austin English wrote:
On Tue, Jun 9, 2009 at 10:57 AM, walt<[email protected]> wrote:
I had an app running happily for over an hour, fetching realtime quotes
for foreign currencies, when it suddenly encountered "a serious problem"
i.e. a crash, and had to close.  This is the error message from the
command line:

err:header:HEADER_WindowProc unknown msg 1264 wp=33f988 lp=0033f9e4
Was there more in the terminal?
Yes indeed, hundreds of fixme's of various flavors, but those can't be the
reason for the crash because the program routinely produces those even
when it's working.

I should mention that from winetricks I've installed vcrun2005sp1, msxml3,
and I'm using the native rpcrt4 just to get the program running.

The messages below are from a separate crash, which looked to me the same
as the first crash, but this time there was no 'header' error:


<lots of fixme snippage>
fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS,
hwnd=0x2002c): stub
fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR,
hwnd=0x2002c, edge=3): stub
fixme:win:GetProcessDefaultLayout ( 0x33dd58 ): No BiDi
fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS,
hwnd=0x2002c): stub
fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR,
hwnd=0x2002c, edge=3): stub
fixme:shdocvw:PersistStreamInit_InitNew (0x35bf938)
fixme:shdocvw:WebBrowser_put_RegisterAsDropTarget (0x35bf938)->(0)
fixme:shdocvw:navigate_url Unsupported args (Flags 0x33d644:2; TargetFrameName
0x33d654:0)
fixme:urlmon:URLMoniker_BindToObject use running object table
fixme:shdocvw:BindStatusCallback_OnProgress status code 11
fixme:shdocvw:BindStatusCallback_OnProgress status code 14
fixme:system:SetProcessDPIAware stub!
fixme:dwmapi:DwmIsCompositionEnabled 0x33b01c
fixme:iphlpapi:NotifyAddrChange (Handle 0x5f8e878, overlapped 0x5f8e880): stub
err:module:DelayLoadFailureHook failed to delay load
rpcrt4.dll.I_RpcExceptionFilter
wine: Call from 0x7edcb233 to unimplemented function
rpcrt4.dll.I_RpcExceptionFilter, aborting
wine: Unimplemented function rpcrt4.dll.I_RpcExceptionFilter called at address
0x7edcb233 (thread 0019), starting debugger...
fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.VC80.MFCLOC" (8.0.50608.0)
err:module:attach_process_dlls "rpcrt4.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program
Files\\Candleworks\\FXTS2\\FXTSpp.exe" failed, status c0000005

And here is another crash that just happened as I'm typing this reply:

<more fixme snippage>
fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR,
hwnd=0x10026, edge=3): stub
fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS,
hwnd=0x10026): stub
fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR,
hwnd=0x10026, edge=3): stub
fixme:win:GetProcessDefaultLayout ( 0x33dd58 ): No BiDi
fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS,
hwnd=0x10026): stub
fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR,
hwnd=0x10026, edge=3): stub
fixme:shdocvw:PersistStreamInit_InitNew (0x32b2808)
fixme:shdocvw:WebBrowser_put_RegisterAsDropTarget (0x32b2808)->(0)
fixme:shdocvw:navigate_url Unsupported args (Flags 0x33d644:2; TargetFrameName
0x33d654:0)
fixme:urlmon:URLMoniker_BindToObject use running object table
fixme:shdocvw:BindStatusCallback_OnProgress status code 11
fixme:shdocvw:BindStatusCallback_OnProgress status code 14
fixme:system:SetProcessDPIAware stub!
fixme:dwmapi:DwmIsCompositionEnabled 0x33b01c
err:module:DelayLoadFailureHook failed to delay load
rpcrt4.dll.I_RpcExceptionFilter
wine: Call from 0x7edd6233 to unimplemented function
rpcrt4.dll.I_RpcExceptionFilter, aborting
fixme:iphlpapi:NotifyAddrChange (Handle 0x5f7e878, overlapped 0x5f7e880): stub
wine: Unimplemented function rpcrt4.dll.I_RpcExceptionFilter called at address
0x7edd6233 (thread 0009), starting debugger...
fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.VC80.MFCLOC" (8.0.50608.0)
Top
austin987
Wine Developer
Wine Developer
Posts: 2383
Joined: Fri Feb 22, 2008 8:19 pm

HEADER_WindowProc unknown msg ?

Post by austin987 »

On Tue, Jun 9, 2009 at 5:47 PM, walt<[email protected]> wrote:

On Tue, 9 Jun 2009, Austin English wrote:
On Tue, Jun 9, 2009 at 10:57 AM, walt<[email protected]> wrote:
I had an app running happily for over an hour, fetching realtime quotes
for foreign currencies, when it suddenly encountered "a serious problem"
i.e. a crash, and had to close.  This is the error message from the
command line:

err:header:HEADER_WindowProc unknown msg 1264 wp=33f988 lp=0033f9e4
Was there more in the terminal?
Yes indeed, hundreds of fixme's of various flavors, but those can't be the
reason for the crash because the program routinely produces those even
when it's working.
That doesn't necessarily mean that error is the cause of the bug. A
crash should show a backtrace, which you didn't have.

If you're sure that err is the cause, use 'winetricks cc580'. Native
comctl32 doesn't work perfectly though, some buttons may be black,
etc.
I should mention that from winetricks I've installed vcrun2005sp1, msxml3,
and I'm using the native rpcrt4 just to get the program running.
Native rpcrt4 does not work properly in wine, especially if installed by itself.
The messages below are from a separate crash, which looked to me the same
as the first crash, but this time there was no 'header' error:
--
-Austin
Top
walt

HEADER_WindowProc unknown msg ?

Post by walt »

Austin English wrote:
On Tue, Jun 9, 2009 at 5:47 PM, walt<[email protected]> wrote:
I should mention that from winetricks I've installed vcrun2005sp1, msxml3,
and I'm using the native rpcrt4 just to get the program running.
Native rpcrt4 does not work properly in wine, especially if installed by itself.
Hm. I removed the rpcrt4 override this morning and so far the app is rock
solid. I think I added that override before I got the app installed, so
it must have been something to do with the installer.

There is one odd thing that happens consistently when I start the program from
a command prompt: the app freezes after logging into its remote data server,
and I can un-freeze it by typing a carriage return in the same xterm window
that I started the program from.

Any ideas why that might happen?

Thanks.
Top
Locked

Return to “Wine Help”