Browser ignores some "minimize" messages

Right at this moment, my 9.26/8835 (Win32)
will minimize only if the main app window's "minimize" button is
clicked, or
if "minimize" is selected in the Taskbar app button's context
(R-click) menu.

It will _not_ minimize in response to Windows' "Minimize all"
(WindowsKey+M), nor in response to clicking the Taskbar app button
so as to "undepress" it (which I suspect might send the same
message),
although all other applications obey these requests.

BTW, "Show desktop" works entirely differently,
and all apps "spring back" as soon as any again gets focus,
so that's not a substitute for actually "minimizing" apps.

Opera doesn't always ignore these particular messages,
but I have many times seen this affliction spring up,
for which the only cure has been to close and restart Opera.

This time, however, I'm aware of an event which occurred
just prior to Opera "becoming deaf" to these messages:

My computer was suddenly using 100% CPU all the time,
the culprit turning out to be Explorer.exe (the "desktop" etc.);
I have no idea what triggered Explorer to "go bananas" like that,
which seemed impossible to stop, but in view of Opera's subsequent
"deafness" to Explorer, I'm wondering whether it could have involved
any communication between Explorer.exe and Opera.exe

I then invoked "Process Explorer" (the Sysinternals/Microsoft
"better Task Manager") to kill and restart Explorer.exe,
and ever since that restart of Explorer.exe,
Opera has been ignoring these partcular "minimize" messages
 from the new instance of Explorer.exe,
although all other applications are as cooperative
with the new Explorer instance as they were with the original.

Thus makes it appear as if Opera might have "locked horns with"
the original Explorer instance, perhaps even causing its
100% CPU loop, and has never let go of whatever it's waiting for,
thus now unable to attend to any similar new messages.

If this happens to "ring a bell" with any developer,
perhaps they will have a clue and recognize what might be involved;
although a minor annoyance, any little improvement towards perfection
always noticeably enhances good feelings towards any product.

Any similar user experience might also be of interest, thanks.

On Sun, 30 Mar 2008 13:29:58 +0200, John H Meyers  
<jhmeyers@nomail.invalid> wrote:

> Right at this moment, my 9.26/8835 (Win32)
> will minimize only if the main app window's "minimize" button is 

> clicked, or
> if "minimize" is selected in the Taskbar app button's context
(R-click)  
> menu.

On OsX 10.5.2 running Opera 9.26.

Opera will not minimize using the minimize button in upper lefthand corner.
This happens after Opera has been open/active for a while, say a day or so.

J.


>
> It will _not_ minimize in response to Windows' "Minimize all"
> (WindowsKey+M), nor in response to clicking the Taskbar app button
> so as to "undepress" it (which I suspect might send the same
message),
> although all other applications obey these requests.
>
> BTW, "Show desktop" works entirely differently,
> and all apps "spring back" as soon as any again gets focus,
> so that's not a substitute for actually "minimizing" apps.
>
> Opera doesn't always ignore these particular messages,
> but I have many times seen this affliction spring up,
> for which the only cure has been to close and restart Opera.
>
> This time, however, I'm aware of an event which occurred
> just prior to Opera "becoming deaf" to these messages:
>
> My computer was suddenly using 100% CPU all the time,
> the culprit turning out to be Explorer.exe (the "desktop" etc.);
> I have no idea what triggered Explorer to "go bananas" like
that,
> which seemed impossible to stop, but in view of Opera's subsequent
> "deafness" to Explorer, I'm wondering whether it could have
involved
> any communication between Explorer.exe and Opera.exe
>
> I then invoked "Process Explorer" (the Sysinternals/Microsoft
> "better Task Manager") to kill and restart Explorer.exe,
> and ever since that restart of Explorer.exe,
> Opera has been ignoring these partcular "minimize" messages
>  from the new instance of Explorer.exe,
> although all other applications are as cooperative
> with the new Explorer instance as they were with the original.
>
> Thus makes it appear as if Opera might have "locked horns with"
> the original Explorer instance, perhaps even causing its
> 100% CPU loop, and has never let go of whatever it's waiting for,
> thus now unable to attend to any similar new messages.
>
> If this happens to "ring a bell" with any developer,
> perhaps they will have a clue and recognize what might be involved;
> although a minor annoyance, any little improvement towards perfection
> always noticeably enhances good feelings towards any product.
>
> Any similar user experience might also be of interest, thanks.
>



--