Crash attempting to load mailshell.xul file Bear with me, please. I'm trying to run Seamonkey mail for the first time. 1) Download fullsea.zip from Mar100805 directory; unzipped it. URL is: ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/Mar100805/ 2) Copied the prefs.js file that was in an email David sent to mailnewsstaff and placed in the same directory as apprunner; modified the prefs.js file to my mail folder path: user_pref("mailnews.rootFolder", "d:\\netscape_users\\qatest03\\mail"); 3) In DOS window, start apprunner 4) Apprunner starts; browser window appears 5) In the URL field, type: mailshell.xul 6) I can see an outline of some sort of a mail window draw; I see broken icon links for New Msg buttons, etc. 7) Then, I get a crash. Talkback Tracking ID: CJP48GJC In the DOS window, it shows: "JS error - missing ( before formal parameters. URL file://D:/seamonkey/Mar100805/bin/res/samples/mailshell.xul, LineNo 128. Am I doing something wrong?

I've only ever tried passing the xul url in on the command line as follows: -width 1000 -height 1000 -url resource:/res/samples/mailshell.xul

Update: I tried some mscott suggestions and copied appcore.dll into the bin directory and added the following lines to the prefs.js file: user_pref("mailnews.pop_server", "nsmail-2"); user_pref("mailnews.smtp_server", "nsmail-2"); user_pref("mailnews.user_name", "qatest03"); Same problem with the crash. Will keep trying....

I typed this in the command line: D:\seamonkey\Mar100805\bin\apprunner.exe -width 1000 -height 1000 -url resource:/res/samples/mailshell.xul Same crash problem: tracking ID: CJQ240IL (or 1L)

Talked to mscott. He says that mcmullen just fixed this problem after today's release builds went out. Scott Putterman had originally found this problem. I'll reassign to putterman to add any comments to this. I don't know if this is a duplicate of any other bug report.

Assuming this was the crash from this morning, both John and I checked in fixes for our respective pieces of code.

Using the release build under "fullsea.zip" in the Mar110805 directory, the same problem happens. Tracking ID: CKO02ABP. Shouldn't your fix(es) be in today's build?

It turns out there was another crash this morning relating to interaction between the database and rdf that I fixed after the build. Sorry about this.

Ackkk my posting got lost because I didn't properly log onto bug splat...*sigh* What I was trying to say in my previous comment that I lost is that we need to come up with a strategy for making sure QA gets good builds from seamonkey. The last two mornings we've found crashes when we have done our morning builds and have checked in fixes as soon as the tree opens. I wonder if we need to get sar running our new smoketest check list and she could keep the tree closed if we fail. Then QA has a better chance of getting builds that aren't DOA on arrival. It's hard to do this in a world that changes as much as this one..hmmm =)

Good idea. The think that sar should run the very basic test which, at this time, would be able to bring up the mail application. I will work with someone to try to get this part automated.

I had been using fullsea.zip (which includes Talkback stuff) instead of seamonkey.zip. In today's release build: ftp://sweetlou/products/client/5.0x/windows/32bit/x86/Mar120805/, extracting and using the files from "fullsea.zip" causes the crash upon mail startup that I've been reporting for the last few days. Using the files from "seamonkey.zip" is fine (mail window appears). Any ideas why?

cc: chofmann - Chris - do you know what difference there may be between seamonkey.zip and fullsea.zip (other than the talkback stuff)? Thanks.

cyeh should know.

the only code difference between the two is the enabling of fullcircle stuff. however, there may be a subtle difference in the packaging of each build, since they go through slightly different processes. you can't do bit compares, but everything should be installed using the same folder structure. the builds are susceptable to registry code issues if every single bit isn't exactly where apprunner and viewer expect to register the code.

Putting on M3 radar. Please verify with Mar 15 builds when they come out. Thanks!

Reopening and assigning to cyeh. Mar150940 build of fullsea.zip has the same problem. Mar150940 build of seamonkey.zip is fine. One difference I noticed is that fullsea.zip extracts to a \bin folder structure whereas seamonkey.zip extracts to a \x86rel folder structure. I noticed that most files in the components directory (\bin\components) were dated the 10th as well as some files in the res directory (\bin\res). Could this be the problem? Reopening....

re-assigning to leaf. Leaf, two steps to figure out what is wrong. 1) Make sure you can run apprunner standalone. 2) obtain a mail.xul file from lchiang and see if you can get together and get it to crash in your environment.

I'm not sure if i need the prefs.js file to test this... i'll give it a run on my 98 box tomorrow morning.

Let me know if you need help to reproduce this problem. Thanks. This problem occurs with more than one prefs.js, so it's not specific to mine. If you'd like to see what should be in the prefs.js file, see: http://slip/projects/seamonkey/mail/admin/dogfood_mail_startup.html

I'm going to mark this fixed/works for me. lets check the next round of builds and reopen if its still a problem

The files zipped in fullsea.zip are old files. I downloaded fullsea.zip from for the Mar180805 build. I unzipped the files. When I start apprunner.exe, I get all those errors about missing the libnspr*.* files. This indicates to me that the files in fullsea.zip are old (because if the files were current, I wouldn't get this error about missing files.) I have no problem with the mar180805 seamonkey.zip file. This is easily reproducible. Has anyone but me try to download fullsea.zip, unzipped it, and run apprunner.exe? I'll be happy to show someone. Just let me know. beppe indicated to me that her group does not test fullsea.zip, only seamonkey.zip. If we are not supposed to be even trying out fullsea.zip at this time, then let me know too. Reopening. This problem is more generic - has nothing to do with mail specific items as I first thought.

If you don't think this should be a M3 stopper, that's fine with me. But, the problem I reported is reproducible all the time for me.

lisa, can you try the fullsea.zip file in the current directory on sweetlou? i think i have fixed the packager.

Thanks. I unzipped fullsea.zip (dated 3/22/99, time 05:51) in the ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/current/ directory at this time. Started apprunner.exe and brought up Messenger with no problems. Verified that the code base is M4 because I'm seeing items in Messenger that were implemented in M4. (Also, all the lib*.* files were no longer there.) I'll officially mark this bug "verified" after you've marked it fixed and I will verify again in another release build.

marking verified. Fenella and others in group have been using the latest fullsea.zip without problems.