38356 - crash in nsDeviceContextWin::ComputeFullAreaUsingScreen

Status: VERIFIED WORKSFORME

(Core :: XUL, defect, P3)

Description

[mulley]

Mozilla recently began to crash on startup. This is not intermittent; it 
happens constantly. It didn't use to happen: builds which used to work no 
longer do.

The latest build that I've tested is the May 5th 2000 M16 nightly. 
(Specifically, the one downloaded from 
ftp://ftp.mozilla.org/pub/mozilla/nightly/2000-05-05-13-M16/mozilla-win32-
talkback.zip) Problems also occur with M15 and Netscape PR1.

The first time I ran this latest build, it produced an error: "The procedure 
entry point ?Compare@nsString@@UBEHABV1@HH@Z could not be located in the 
dynamic link library xpcom.dll". After clicking OK on the error message box, it 
continue to load, the splash screen disappeared, the border of the program 
window appeared, and it crashed. Dr. Watson reported an access violation in 
mozilla.exe; Dr. Watson logs are available if necessary. On subsequent runs, 
mozilla still crashes in the same way, but the initial error message is not 
displayed. (The error message is still not displayed if \WINNT\mozregistry.dat 
and the Users50 directory are deleted.)

Steps to reproduce: Run mozilla.exe. It crashes. (Likely will not reproduce on 
other systems.)


Talkback ID numbers are TB9968896H (initial run) and TB9968961M (subsequent 
run).

This was originally reported in the mozilla newsgroups; here are some responses 
to questions asked there.
********************************
Original post:
I'm running Windows 2000, and Mozilla has recently decided that it doesn't
like me.

- M15 starts, displays a splash screen, then quits (not crashes, just quits
silently)
- Netscape PR1 starts, displays a splash screen, then crashes with the
splash still displayed
- An M16 nightly downloaded about 20 minutes ago starts, displays the splash
screen, then erases the splash screen, begins to display the main window...
and then crashes.

I have used various milestones, nightly builds, etc. for quite a while
without problems. This seems to have just happened spontaneously -- existing
installs of M15 and PR1 just stopped working today. I've tried deleting all
the Users50 directories I could find, deleting \WINNT\mozregistry.dat, and
deleting all Registry keys involving Seamonkey or Mozilla. I even removed
4.7 just in case profile migration was causing problems. (that's why I'm
posting with MS outlook)

When run with -console, M15 and PR1 quit/crash after the "Profile Manager:
End" (paraphrased) line. M16 nightly crashes after the "has multiple
monitors apis is 1" line.
*********************************
Second post:
> 1) are you running 'Professional' or 'Server'?

Professional.

> 2) did you run pre-release versions of win2k on the same box (and
>    upgrade to final from there)?
No. Clean install of final on a new partition.

> 3) what are the build ID numbers for msvcrt.dll and msvcirt.dll?
Both files are version 6.10.8637.0 (these are the versions in
\WINNT\system32).

> 4) what other applications are installed?
    Applications installed: well, tons. It's a heavily used computer. But
mozilla has run well for quite a while, and I don't have anything which
heavily modifies the system installed (with the possible exception of
AtGuard, which is firewall software).

    To the best of my knowledge, only two apps have been installed since
mozilla last worked: quicktime 4 (but that was a reinstall after an
uninstall -- it had previously coexisted with mozilla) and MS office 2000
(on top of an existing office 97 installation). The Office install (Standard
Version) was fairly, well, standard: off of a retail CD, no problems
encountered during install.

> 5) ...

Not too many other details I can think of. I've had no odd hardware or
software problems recently. The hardware is modern enough, no performance
problems. Everything other than Mozilla is behaving as normal. The only real
trigger that I can think of is the install of Office 2000, and this is such
a common program that it seems unlikely to cause problems. No system
configuration changes. (Well, minor, routine stuff: changing IP addresses,
changing locale and keyboard settings.)
***********************************
Reply from [e-mail] (edited):
the firewall -- there have been some past problems with 
    getting necko to play nice with the socket connections.
    Can you possibly try disabling/bypassing the software
    and see if that clears up the problem.
    (see maybe http://bugzilla.mozilla.org/show_bug.cgi?id=32048 
     for background)
***********************************
(When the firewall is exited, the problem still occurs.)

Comment 1

[John Morrison]

Hi. Well, good news/bad news -- I know what this is, but there's no fix for it 
at the moment (but Real Soon Now). Thanks for taking the time to file this bug 
report.

The crash is caused by the dual monitor's you have setup. The call to 
nsDeviceContextWin::ComputeFullAreaUsingScreen at top of stack is a clear
giveaway. marking duplicate of bug #36479

The second thing (Compare@nsString@@UBEHABV1@HH@Z) is (despite appearances) an 
innocuous build system error. An obsolete .dll is being shipped with the 
-talkback.zip builds, and the component registry process barfs on a bogus 
linkage. This error will go away whenever the build team cleans up their 
packaging (I can't remember the bug number offhand). 

Anyways, thanks again, and hope the fix comes soon so you can get running again.
(although, I believe you can run if you just disable the second monitor [if you 
want]).

*** This bug has been marked as a duplicate of 36479 ***

Comment 2

[Blake Ross]

Nice report though, [e-mail]

vrfy

Comment 3

[mulley]

I have only one monitor.

Video card info: ATI Xpert 128. This is a fairly standard Rage128 chip based 
card. It only supports one monitor. I'm using the drivers from the Win2000 CD. 
I'm using no utilities or external programs related to video or display. I have 
no other video-related hardware other than the card. (And, of course, the 
monitor, which is a Viewsonic VPA138, which has no special drivers installed.)

Win2000 Device Manager indicates only one video card and display; the Display 
control panel doesn't mention anything about multiple monitors.

(By the way, a side note. I'm a bugzilla newbie, and tried to reopen this bug. 
Bugzilla wouldn't let me; it told me that only the owner or submitter could do 
this. I am the submitter, and am logged in. As such, it's still marked 
duplicate.)

Comment 4

[John Morrison]

Doh! Y'know as I was writing the above, I was thinking "what if he doesn't have 
multiple monitors ... nah! couldn't be ...". Well, I'm feeling pretty dumb.
Reopening ...

Comment 5

[Blake Ross]

heh...I totally missed that too when I verified it.  I'm not quite sure why the 
hell I assumed he/she had multiple monitors.

Fixing up as crash (severity, kw)...

Comment 6

[John Morrison]

Actually, in principle, you can't get to that location in the code unless you 
do have multiple monitors enabled ...

Comment 7

[Blake Ross]

I'm gonna shut up now before I say more dumb stuff.

(how did he/she reach that point, then?)

Comment 8

[Asa Dotzler [:asa]]

we check for multiple monitors and must somehow be concluding that this is a 
multipe monitor setup.  If the reporter can run mozilla with the -console 
command line option I think that check will show it's results there. 

Comment 9

[John Morrison]

The message that comes out on the console is a reference to whether the 
required win32 API's are present, but for win2k that's a given. At any rate, 
I'm passing this off to pinkerton, who is master of the multiple screens.

Mike: this report started out with someone who previously had been able to 
run mozilla on win2k, but had begun crashing on startup with more recent builds.
The curious thing is the the stack trace is the same one for people who have
multiple monitors and crash ... but in this case, it's a single monitor setup 
(which begs the question "how come mozilla believes there are multiple monitors 
when there is only one").

Comment 10

[John Morrison]

*** Bug 38366 has been marked as a duplicate of this bug. ***

Comment 11

[John Morrison]

bug #38366 (the duplicate) is another crash, on win2k, in 
ComputeFullAreaUsingScreen, for a user with a single monitor setup.
http://cyclone/reports/SingleIncidentInfo.cfm?dynamicBBID=9972968

Setting M18 so it makes the review list for nsbeta2 bugs.

Comment 12

[Mike Pinkerton (not reading bugmail)]

i'll accept this, but it's probably a dupe of the other.....as discussed....does 
anyone here at nscp have a system where this crashes? cc'ing mjudge because he's 
running a dual-headed win2k box

Comment 13

[Jus]

I am suffering the same problem on a single monitor laptop. Could the fact that 
my laptop (as do lots of others) have a VGA output for an external monitor 
provide any insight?
Im running Win2K (2195) clean install + Eudora + NAV 2000 + Graphics
All was fine till dail just before Milestone M15

Comment 14

[Shiva Thirumazhusai]

Adding topcrash keyword into the list.

This crash happens a lot in the recent builds.

Stack Trace:-

nsDeviceContextWin::ComputeFullAreaUsingScreen 
[d:\builds\seamonkey\mozilla\gfx\src\windows\nsDeviceContextWin.cpp, line 211] 
nsDeviceContextWin::GetRect 
[d:\builds\seamonkey\mozilla\gfx\src\windows\nsDeviceContextWin.cpp, line 742] 
ScreenImpl::GetLeft [d:\builds\seamonkey\mozilla\dom\src\base\nsScreen.cpp, line 
114] 
nsMenuPopupFrame::SyncViewWithFrame 
[d:\builds\seamonkey\mozilla\layout\xul\base\src\nsMenuPopupFrame.cpp, line 559] 
nsMenuFrame::OpenMenuInternal 
[d:\builds\seamonkey\mozilla\layout\xul\base\src\nsMenuFrame.cpp, line 592] 
nsMenuFrame::AttributeChanged 
[d:\builds\seamonkey\mozilla\layout\xul\base\src\nsMenuFrame.cpp, line 477] 
nsCSSFrameConstructor::AttributeChanged 
[d:\builds\seamonkey\mozilla\layout\html\style\src\nsCSSFrameConstructor.cpp, 
line 9500] 
StyleSetImpl::AttributeChanged 
[d:\builds\seamonkey\mozilla\layout\base\src\nsStyleSet.cpp, line 1076] 
PresShell::AttributeChanged 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 2819] 
nsXULDocument::AttributeChanged 
[d:\builds\seamonkey\mozilla\rdf\content\src\nsXULDocument.cpp, line 1490] 
nsXULElement::SetAttribute 
[d:\builds\seamonkey\mozilla\rdf\content\src\nsXULElement.cpp, line 2860] 
nsXULElement::SetAttribute 
[d:\builds\seamonkey\mozilla\rdf\content\src\nsXULElement.cpp, line 1475] 
nsMenuFrame::OpenMenu 
[d:\builds\seamonkey\mozilla\layout\xul\base\src\nsMenuFrame.cpp, line 499] 
nsMenuFrame::ToggleMenuState 
[d:\builds\seamonkey\mozilla\layout\xul\base\src\nsMenuFrame.cpp, line 385] 
nsMenuFrame::HandleEvent 
[d:\builds\seamonkey\mozilla\layout\xul\base\src\nsMenuFrame.cpp, line 277] 
PresShell::HandleEventInternal 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 3422] 
PresShell::HandleEvent 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 3340] 
nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 774] 
nsViewManager::DispatchEvent 
[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 1765] 
HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 69] 
nsWindow::DispatchEvent 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 531] 
nsWindow::DispatchWindowEvent 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 548] 
nsWindow::DispatchMouseEvent 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3360] 
ChildWindow::DispatchMouseEvent 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3565] 
nsWindow::ProcessMessage 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2478] 
nsWindow::WindowProc 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 781] 
KERNEL32.DLL + 0x363b (0xbff7363b) 
KERNEL32.DLL + 0x24407 (0xbff94407) 
0x00688bda 

Comment 15

[Peter Trudelle]

[nsbeta2+]

Comment 16

[Mike Pinkerton (not reading bugmail)]

I feel just sick about this, but i made a 98 development machine and i cannot 
duplicate the problem. at all. it works fine with two monitors.

marking WORKSFORME as it works on win98 and win2k.

Comment 17

[Chris Hubick]

I suffer the same problem as Tim Echanter, where it started crashing at some 
point before m15 on a single monitor laptop (Sony Viao model pcg 505hs) running 
win2k.  I filed a separate bug 38366 which as you can see was marked as a 
duplicate of this.  I also installed Word 2000 somewhere around the time Moz 
stopped working, but I *think* Moz may still worked after that.

Personally, I think the presence of the external monitor port on the laptop 
must have something to do with Moz getting into the dual monitor code path.
As an active web developer with a great deal of interest in Mozilla, this bug 
has been Real Bad Thing for me.  If there is any information I can provide 
other than that which I provided with bug 38366, or testing I can do, please 
let me know.

Comment 18

[Mike Pinkerton (not reading bugmail)]

since i just can't procure hardware, and all the hardware i have seems to not 
trigger this bug, i'm at a loss. i need someone on the net with a development 
environment who has the problem to help.

Comment 19

[Chris Hubick]

I got Mozilla to build on my Sony Viao PCG-505HS laptop running Win2k.  The 
good news is that this build starts and runs (I haven't tried any since I 
submitted bug 38366).  The build is the ftp tarball for 2000042708.

The following is displayed on startup:
--------------------------------------------

nsNativeComponentLoader: autoregistering begins.
nsNativeComponentLoader: autoregistering succeeded
nNCL: registering deferred (0)
Profile Manager : Profile Wizard and Manager activites : Begin
Profile Manager : Command Line Options : Begin
DEBUG BUILDS ONLY:  we are forcing you to use the profile manager to help smoke
test it.
Profile Manager : Command Line Options : End
has multiple monitor apis is 1
****** number of screens 2
WEBSHELL+ = 1
plugins at: C:\mozilla_source\mozilla\dist\WIN32_D.OBJ\bin\plugins
Note: verifyreflow is disabled
Note: styleverifytree is disabled
Note: frameverifytree is disabled
has multiple monitor apis is 1
*** found screen 10001
has multiple monitor apis is 1
*** found screen 10001
Move window by 456,356.5
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
start with profile: default
ProfileManager : StartApprunner
profileName passed in: defaultProfileManager : GetProfileDir
ProfileName : default
ProfileDir  : C:\utils\mozilla\Users50\default
ProfileManager : GetProfileDir
~nsProfile
WEBSHELL- = 0
Profile Manager : Profile Wizard and Manager activites : End
WEBSHELL+ = 1
Initialized app shell component {18c2f989-b09f-11d2-bcde-00805f0e1353}, rv=0x000
00000
FOR DEBUG BUILDS ONLY:  we are forcing you to see the checkin guidelines when yo
u open a browser window
WEBSHELL+ = 2
CSSLoaderImpl::LoadAgentSheet: Load of URL 'file:///C|/utils/mozilla/Users50/def
ault/chrome/user.css' failed.  Error code: 18
assuming d&d is off for Personal Toolbar
Obtained name of Personal Toolbar from bookmarks string bundle.
Start reading in bookmarks.html
Finished reading in bookmarks.html  (140000 microseconds)

-->loadDS(): ds=[xpconnect wrapped nsIRDFDataSource], loaded=true, returning! <-
-
WEBSHELL+ = 3
WEBSHELL+ = 4
Setting content window
FOR DEBUG BUILDS ONLY:  we are forcing you to see the checkin guidelines when yo
u open a browser window
*** Pulling out the charset
Loading page specified via openDialog
Opening file cookperm.txt failed
-*- sidebar: CI: {577cb745-8caf-11d3-aaef-00805f8a4905}
-*- sidebar: sidebar uri is file:///C|/utils/mozilla/Users50/default/panels.rdf
-*- sidebar: datasource_uri is file:///C|/utils/mozilla/Users50/default/panels.r
df
in SetSecurityButton
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
*** found screen 10001
--------------------------------------------
...And so on...

I offer my limited time and services to help resolve this.

Comment 20

[Andreas Franke (gone)]

I suggest to reopen this bug. Or isn't it a topcrash any more? If it stays
resolved, it won't show up in any queries, and it can't be found in queries,
e.g. searches for duplicates or "helpwanted" keywords.

Comment 21

[John Morrison]

Can [e-mail] and [e-mail] see how this looks in tomorrow's 
win32 builds. This should be fixed by the fix for bug 36479 (in reality this
is a duplicate bug). Thanks.

Comment 22

[John Morrison]

marking verified (see bug #36479)

Comment 23

[mulley]

Today's build works for me. (I was crashing before, submitted this bug.) Yes!

Comment 24

[Chris Hubick]

Todays build WORKSFORME.  Good work!

Comment 25

[Shiva Thirumazhusai]

Moving all the Works For Me bugs to talkback user account for future reference.

Comment 26

[Shiva Thirumazhusai]

We are gathering all the Resolved and WFM bugs which are happened to be topcrash 
bugs and assigning it to talkback. I am marking all of them as RESOLVED WFM.

Comment 27

[Blake Ross]

VERIFIED wfm (6/8 build, win2k)