956822 - Local file as mail start page doesn't show up

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Matthias Bockelkamp]

In recent trunk builds, a local mail start page (file:///C:/Folder/page.htm) does not show up any more. Also messages are not displayed and SeaMonkey cannot be closed (has to be killed). If the start page is disabled and SeaMonkey restarted, everything is working normal again.

Regression range is somewhere between 20131104003001 and 20131208003001.

Note this is not a reoccurence of bug 763617. The error console doesn't show any message, inserting a valid charset into the local file also doesn't help.

Comment 1

[Matthias Bockelkamp]

I have tried some more builds. The actual regression range is between 20131125014248 and 20131126003856.

Comment 2

[Philip Chee]

http://hg.mozilla.org/comm-central/pushloghtml?startdate=2013-11-25&enddate=2013-11-27
Nothing jumps out at me. Perhaps it was something in mozilla-central.

Comment 3

[Tony Mechelynck [:tonymec]]

Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 SeaMonkey/2.27a1 ID:20140214003001 c-c:1ce77c2f9bd0 m-c:d275eebfae04

In order for the "Go → Mail Start Page" menu to be other than greyed-out, the message-read (preview) pane must be open (and not collapsed) in the three-pane window or tab.

1) Mail start page set to file:///root/pub/index.htm
- At startup, the preview pane being collapsed, the start page appears fleetingly.
- Opening the preview pane doesn't display the page (a blank page is still displayed) but it un-greys-out the "Go → Mail Start Page" menuitem
- Clicking that menuitem displays the page

2) Set mail start page to the default, chrome://messenger/content/start.xhtml
- The preview pane doesn't change
- Click "Go → Mail Start Page" again
- The default page is now displayed.

3) Set mail start page to about: (the "About SeaMonkey" page)
- The preview pane doesn't change
- Click "Go → Mail Start Page" again
- The "About SeaMonkey" page is now displayed.

4) Set mail start page to http://users.skynet.be/antoine.mechelynck/ (the same content as in 1 above but from a remote site)
- The preview pane doesn't change
- Click "Go → Mail Start Page" again
- The desired page is now displayed.

1-3 above are three local pages but presented with three different URL schemes (file:, chrome: and about:). 4 is remote (with http: scheme). All four work equally well AFAICT.

Conclusion: I cannot reproduce the bug on this Linux build, subject to some interpretation about what the Mail Start Page menu is supposed to do and about when it is or isn't greyed-out. Also I haven't experienced the closedown hang: with the Mail Start Page set as in 1 above, which is local, Ctrl+Q did quit, after I accepted "Are you sure" dialogs in both the mailer and the browser, each of which had multiple tabs open at the time (more than 100 tabs in the browser). The ChatZilla window was closed without a prompt AFAIK. The closedown did take several minutes between hitting Ctrl+Q and seeing total RAM use on the system go suddenly down from 90% to 20% of 3.2 GiB but that is expected with this many browser tabs and (how many? 50?) enabled extensions.

IOW the bug seems to be Windows-only, unless someone other than me can reproduce it on Linux or Mac. Matthias, you still see it on the latest Windows nightlies, don't you?

Comment 4

[Matthias Bockelkamp]

I just tried the latest windows nightly (20140218003001) and now it even crashes when i use a file:// scheme as mail start page.

Comment 5

[Tony Mechelynck [:tonymec]]

(In reply to Matthias Bockelkamp from comment #4)
> I just tried the latest windows nightly (20140218003001) and now it even
> crashes when i use a file:// scheme as mail start page.

Do you have a bp-something crash ID? (from about:crashes)

Comment 6

[Matthias Bockelkamp]

The crash reporter tool did not start, so I don't have a crash ID.

Comment 7

[J. Weaver Jr.]

Mozilla/5.0 (Windows NT 5.1; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26
Build identifier: 20140428215944
Windows 7/32

Problem confirmed on a fresh profile with _no_ extensions. This problem started for me with 2.25, and has continued in 2.26.

Crash reporter does not start. Windows reports the following:

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	seamonkey.exe
  Application Version:	29.0.0.5231
  Application Timestamp:	535f3e80
  Fault Module Name:	ntdll.dll
  Fault Module Version:	6.1.7601.18247
  Fault Module Timestamp:	521ea91c
  Exception Code:	c0000005
  Exception Offset:	0003224d
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

 -JW

Comment 8

[J. Weaver Jr.]

Further info: error does _not_ occur with .gif or .jpg files. Error _does_ occur with .txt and .htm(l) files.  -JW

Comment 9

[therube]

(I seem to have no problems, on Win XP)

Does it happen in Safe Mode?
(Help | Restart with Addons Disabled)

What Plugins do you have?

Further, does it happen if you also disable all Plugins?
(Tools | Addons Manager -> Plugins)

Does it happen if you restart your computer in Safe Mode with Networking?

Your ID finds more then just "mozilla":
https://www.google.com/search?q=0a9e372d3b4ad19135b953a78882e789&ie=utf-8&oe=utf-8&rls=org.mozilla:en-US:unofficial&client=seamonkey-a

What OS are you running?
Your UA kind of indicates XP, but your ntdll.dll/OS indicate otherwise.

Comment 10

[J. Weaver Jr.]

(In reply to therube from comment #9)

> Does it happen in Safe Mode?
> (Help | Restart with Addons Disabled)

Yes.

> Further, does it happen if you also disable all Plugins?
> (Tools | Addons Manager -> Plugins)

Yes.

> Does it happen if you restart your computer in Safe Mode with Networking?

Yes.
 
> What OS are you running?
> Your UA kind of indicates XP, but your ntdll.dll/OS indicate otherwise.

That UA is odd, now that I look at it - I'm running Windows 7 32-bit. "whatsmyos.com" thinks it's XP, but if I go there with IE, it's correct. Hmmm...  -JW