Open Bug 419347 Opened 17 years ago Updated 2 years ago

Two HCBT_MINMAX messages on minimize

Categories

(Core :: Widget: Win32, defect)

x86
Windows Vista
defect

Tracking

()

UNCONFIRMED

People

(Reporter: david, Unassigned)

Details

(Keywords: stackwanted)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12 When minimizing Firefox, the window sends two HCBT_MINMAX messages instead of one. Reproducible: Always Steps to Reproduce: 1. Open Firefox 2. Minimize it Actual Results: The Firefox window produces two HCBT_MINMAX messages Expected Results: The Firefox window should only produce one HCBT_MINMAX message Applications such as Spy++ don't appear to show HCBT messages. To verify this bug, you may need to use the C# sample that I was working on when I discovered it: http://geekswithblogs.net/dbrown/archive/2008/02/24/detecting-when-any-window-has-been-minimized.aspx
um, i don't suppose you could get us stack traces to these two calls? http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg describes our symbol server.... stack traces would be most useful if generated based on a nightly build, http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ if it doesn't then there's nothing for us to do (the 2.x branch is only taking security fixes)
Component: General → Widget: Win32
Keywords: stackwanted
Product: Firefox → Core
QA Contact: general → win32
Version: unspecified → 1.8 Branch
Sorry, but I am unfamiliar with WinDbg and as this isn't a crash or a hang issue, I couldn't find any way to get a stacktrace. I've also tested Firefox 3 Beta 3 and the latest nightly build and this issue still occurs. Again, sorry I can't be of more help.
Version: 1.8 Branch → Trunk
to get a stack trace (.hh kp), use: kp to set a breakpoint on X in library Q (.hh bp), use: bp Q!X a starting point is probably: bp nsWindow::SetSizeMode I don't suppose config.trim_on_minimize is true (check in about:config), if so, it's probably this: http://bonsai.mozilla.org/cvsblame.cgi?file=/mozilla/widget/src/windows/nsWindow.cpp&rev=3.727&mark=4868#4865 you can download a version of that file from http://mxr.mozilla.org/seamonkey/source/widget/src/windows/nsWindow.cpp?raw=1 and use it with windbg and the symbol server to follow along once your breakpoint is hit.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.