Closed Bug 256511 Opened 20 years ago Closed 20 years ago

Daily page fault crashes in message composition (Reply To:) window. Usually after typing in one or two paragraphs [@ MSVCRT.DLL ]

Categories

(MailNews Core :: Composition, defect)

Product:
MailNews Core
Component:
Composition
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: ceagle, Assigned: sspitzer)

Details

(Keywords: crash, stackwanted)

Crash Data

User-Agent:       Opera/5.02 (Windows 98; U)  [en]
Build Identifier: Mozilla 1.7.1: 2004070721

Crash does not *seem* to occur if "New Message" mode is used to reply to a message. Crashes have been occuring since first install about two weeks ago. Frequency is approximately a page fault every 3 or 4 attempts at message composition. 

Sequence is:

New message displayed in "Inbox" read-mail window pane. Click on "Reply To:" 

After typing anything from half a line to up to 10-15 lines, software abruptly pops up the Windows Page Fault message. Clicking on "Close App", system returns to desktop only and all completed message data is lost, and Mozilla Browser is closed. 

Following is windows page fault error dump from latest event, a few minutes ago:

MOZILLA caused an invalid page fault in
module MSVCRT.DLL at 026f:7800d16a.
Registers:
EAX=00760008 CS=026f EIP=7800d16a EFLGS=00010293
EBX=00000004 SS=0277 ESP=0064e5bc EBP=0064e5d8
ECX=00762798 DS=0277 ESI=036cf00c FS=3277
EDX=0000000d ES=0277 EDI=00000013 GS=0000
Bytes at CS:EIP:
8b 5c d1 04 8d 0c d1 89 5e 04 89 4e 08 89 71 04 
Stack dump:
00000000 00000100 036cf060 00762798 00000000 00000050 000000e0 0064e638 78011b77 00760138 036cf00c 01b70ef0 036cf060 00000090 036c70a4 0000003e 



Reproducible: Sometimes
Steps to Reproduce:
1.Receive email 
2.Open incoming email message in mail reader pane
3.Click on Repy to:
4. Begin reply message composition in message pane.
5. After one or more completed lines of text are typed, event occurs.

Actual Results:  
Mozilla is shut down by Windows.

Expected Results:  
Sorry, but expected results would be that I could respond to messages without Mozilla/Mail component crashing and shutting down. 

(See Windows stack dump thing in previous section)...

Invalid Page Fault in MSVCRT.DLL

Note: I *have* seen other modules reported as the fault, in addition to the above (most common), previously, but cannot recall them. Will report each one... if desired.

-------------------------------------------
Build platform
target
i586-pc-msvc

Build tools
Compiler 	Version 	Compiler flags
$(CYGWIN_WRAPPER) cl 	12.00.8804 	-TC -nologo -W3 -nologo -Gy -Fd$(PDBFILE)
$(CYGWIN_WRAPPER) cl 	12.00.8804 	-TP -nologo -W3 -nologo -Gy -Fd$(PDBFILE)

Configure arguments
--without-system-jpg --without-system-zlib --enable-extensions=default,irc,tasks --enable-crypto --disable-auto-deps --disable-debug --enable-optimize=-O1
Please compile without --disable-debug and post a stacktrace.
Keywords: crash, stackwanted
URL: [N/A]
Following are the continuing crashes with email composition, this past week:

[Date missing this item only]
MOZILLA caused an invalid page fault in
module MSVCRT.DLL at 026f:7800d16a.
Registers:
EAX=00760008 CS=026f EIP=7800d16a EFLGS=00010293
EBX=00000006 SS=0277 ESP=0064e5bc EBP=0064e5d8
ECX=00762ba0 DS=0277 ESI=036ff00c FS=4bbf
EDX=0000000f ES=0277 EDI=00000015 GS=0000
Bytes at CS:EIP:
8b 5c d1 04 8d 0c d1 89 5e 04 89 4e 08 89 71 04 
Stack dump:
00000000 00000100 036ff080 00762ba0 00000000 00000070 00000100 0064e638 78011b77 00760138 036ff00c 03750ef0 036ff080 00000090 036fe9a4 0000003e 


8/24/04 - 1714

MOZILLA caused an invalid page fault in
module MSVCRT.DLL at 026f:7800d16a.
Registers:
EAX=00760008 CS=026f EIP=7800d16a EFLGS=00010202
EBX=00760138 SS=0277 ESP=0064e5bc EBP=0064e5d8
ECX=00762ba0 DS=0277 ESI=0351d19c FS=61f7
EDX=00000008 ES=0277 EDI=00000015 GS=0000
Bytes at CS:EIP:
8b 5c d1 04 8d 0c d1 89 5e 04 89 4e 08 89 71 04 
Stack dump:
00000000 00000100 0351d1a0 00762ba0 00000001 00000031 00000090 0064e638 78011b77 00760138 0351d22c 01b80ef0 0351d1a0 00000090 034e3474 0000003e 


8/25/2004 - 1815

MOZILLA caused an invalid page fault in
module MSVCRT.DLL at 026f:7800d16a.
Registers:
EAX=00760008 CS=026f EIP=7800d16a EFLGS=00010283
EBX=00000002 SS=0277 ESP=0064e5bc EBP=0064e5d8
ECX=00763dc4 DS=0277 ESI=01c7700c FS=646f
EDX=00000010 ES=0277 EDI=0000001e GS=0000
Bytes at CS:EIP:
8b 5c d1 04 8d 0c d1 89 5e 04 89 4e 08 89 71 04 
Stack dump:
00000000 00000100 01c77040 00763dc4 00000000 00000030 00000110 0064e638 78011b77 00760138 01c7700c 03690ef0 01c77040 00000090 01c594c4 0000003e 

8/26/2004 - 2153

MOZILLA caused an invalid page fault in
module MSVCRT.DLL at 026f:7800d16a.
Registers:
EAX=00760008 CS=026f EIP=7800d16a EFLGS=00010293
EBX=00000001 SS=0277 ESP=0064e5bc EBP=0064e5d8
ECX=00763dc4 DS=0277 ESI=02b00e0c FS=698f
EDX=0000000a ES=0277 EDI=0000001e GS=0000
Bytes at CS:EIP:
8b 5c d1 04 8d 0c d1 89 5e 04 89 4e 08 89 71 04 
Stack dump:
00000000 00000100 02b00e30 00763dc4 00000000 00000020 000000b0 0064e638 78011b77 00760138 02b00e0c 01b70ef0 02b00e30 00000090 03747074 0000003e 

8/26/04 - 2250
MOZILLA caused an invalid page fault in
module MSVCRT.DLL at 026f:7800d16a.
Registers:
EAX=00760008 CS=026f EIP=7800d16a EFLGS=00010293
EBX=00000005 SS=0277 ESP=0064e5bc EBP=0064e5d8
ECX=007639bc DS=0277 ESI=00a7700c FS=c04f
EDX=0000000e ES=0277 EDI=0000001c GS=0000
Bytes at CS:EIP:
8b 5c d1 04 8d 0c d1 89 5e 04 89 4e 08 89 71 04 
Stack dump:
00000000 00000100 00a77070 007639bc 00000000 00000060 000000f0 0064e638 78011b77 00760138 00a7700c 01b90ef0 00a77070 00000090 00a735a4 0000003e 


8/28/04 - 1224
MOZILLA caused an invalid page fault in
module MSVCRT.DLL at 026f:7800d16a.
Registers:
EAX=00760008 CS=026f EIP=7800d16a EFLGS=00010202
EBX=00760138 SS=0277 ESP=0064e5bc EBP=0064e5d8
ECX=007639bc DS=0277 ESI=0355561c FS=595f
EDX=00000008 ES=0277 EDI=0000001c GS=0000
Bytes at CS:EIP:
8b 5c d1 04 8d 0c d1 89 5e 04 89 4e 08 89 71 04 
Stack dump:
00000000 00000100 03555620 007639bc 00000001 00000041 00000090 0064e638 78011b77 00760138 035556ac 01b80ef0 03555620 00000090 0356f124 0000003e 


8/29/04 - 0240
MOZILLA caused an invalid page fault in
module MSVCRT.DLL at 026f:7800d16a.
Registers:
EAX=00760008 CS=026f EIP=7800d16a EFLGS=00010202
EBX=00760138 SS=0277 ESP=0064e5bc EBP=0064e5d8
ECX=007633b0 DS=0277 ESI=0331b05c FS=659f
EDX=00000008 ES=0277 EDI=00000019 GS=0000
Bytes at CS:EIP:
8b 5c d1 04 8d 0c d1 89 5e 04 89 4e 08 89 71 04 
Stack dump:
00000000 00000100 0331b060 007633b0 00000001 00000041 00000090 0064e638 78011b77 00760138 0331b0ec 03470ef0 0331b060 00000090 03317024 0000003e 

8/29/04 - 0242
MOZILLA caused an invalid page fault in
module MSVCRT.DLL at 026f:7800d16a.
Registers:
EAX=00760008 CS=026f EIP=7800d16a EFLGS=00010293
EBX=00000000 SS=0277 ESP=0064e5bc EBP=0064e5d8
ECX=00762798 DS=0277 ESI=0298f00c FS=6567
EDX=0000000e ES=0277 EDI=00000013 GS=0000
Bytes at CS:EIP:
8b 5c d1 04 8d 0c d1 89 5e 04 89 4e 08 89 71 04 
Stack dump:
00000000 00000100 0298f020 00762798 00000000 00000010 000000f0 0064e638 78011b77 00760138 0298f00c 03510ef0 0298f020 00000090 029ef044 0000003e 

does it happen with a fresh profile (mozilla -profilemanager) and can you post
Talkback Incident ID with a mozilla.org build ? You should have
"mozilla\components\talkback.exe"
Olivier:

Will attempt a new profile. Results later.

I do not have 'Talkback.exe' anywhere on the computer, per the WinExplorer 'Find' tool. Sorry.

Al
then, reinstall Mozilla to get Talkback
Okay... finally... a *possible* answer/solution! 

Did Google on MSVCRT.DLL and came up with tons of problems with this file's interactions with many applications. Two different items referred to almost identical Page Fault crashes as this Bug Report refers to... in Netscape Messenger. The solution/fix was simple in BOTH instances. (jury is still out here-- but no crashes today so far!) 

Force the Mozilla to use the Windows SYSTEM version of MSVCRT.DLL, instead of the native one, by renaming the version included with Mozilla D/L package! Microsoft contends developers often misapply the 'small' stack heap limits/bounds, then overwrites occur, and the result is the page fault crash. 

I have renamed the file in Mozilla/Java/Bin (I think it was there) to scrap it, and now, Mozilla *appears* to be running fine. No page faults in the message comp Window.

Will update this in a day or two with status report after more testing/use of Mozilla in this mode. 

Al


Further:

Killing the native MSVCRT.DLL now seems to have not only fixed the page fault
 crashes... but also has solved another issue I had experienced, when I 
first installed Moz. 

I have a 21" monitor. Moz. always had problems presenting properly sized text in its various windows and menus at the resolution of this monitor. I have created
 a new profile, per one respondent's suggestion... and now the fonts are working 
beautifully... and are properly sized... with no tinkering with the display font 
settings in preferences. 

Several addtional sessions this afternoon and evening have produced no further 
page fault crashes. 

Al
Marking WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Summary: Daily page fault crashes in message composition (Reply To:) window. Usually after typing in one or two paragraphs. → Daily page fault crashes in message composition (Reply To:) window. Usually after typing in one or two paragraphs [@ MSVCRT.DLL ]
Final contribution:

Now, after two further days of use, and a dozen or so emails, Mozilla has run... perfectly. No crashes. And, the screens are decidedly improved and cleaner. 

Perhaps the MSVCRT.DLL shipped with Mozilla needs to be rechecked? I suspect there may be more than one issue involved with it... specifically perhaps, with systems with large screen, hi-res monitors. It is possible to enter *many* more characters on a typed message line on a 21" monitor than with a 17" monitor... and perhaps that's what the code was written for???  Just a thought.

Thank you.

Al
Product: MailNews → Core
Product: Core → MailNews Core
Crash Signature: [@ MSVCRT.DLL ]
You need to log in before you can comment on or make changes to this bug.