Closed Bug 29296 Opened 25 years ago Closed 25 years ago

MailNewsTest prefs are crashing the AliveTest

Categories

(SeaMonkey :: General, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: mcafee, Assigned: mcafee)

Details

(Keywords: crash, regression, smoketest)

Linux. Adding the two prefs for MailNewsTest, user_pref("signed.applets.codebase_principal_support", true); user_pref("security.principal.X0", "[Codebase http://www.mozilla.org/quality/mailnews/APITest.html] UniversalBrowserRead=1 UniversalXPConnect=1"); crashes the app and fails the AliveTest: #0 0x4016bafd in nsFileSpecHelpers::Canonify (ioPath=@0xbfe027a8, inMakeDirs=0) at nsFileSpecUnix.cpp:87 #1 0x4016dd51 in nsFileSpec::operator= (this=0xbfe027a8, inString=0x0) at nsFileSpec.cpp:990 #2 0x40662bdb in nsSpecialFileSpec::operator= (this=0xbfe027a8, inPath=0x0) at ../../../dist/include/nsFileLocations.h:125 #3 0x40661f50 in nsSpecialFileSpec::operator= (this=0xbfe027a8, aType=App_UserProfileDirectory50) at nsFileLocations.cpp:288 #4 0x40662b04 in nsFileLocator::GetFileLocation (this=0x842eb40, aType=65548, outSpec=0xbfe02808) at nsFileLocations.cpp:570 #5 0x40f3be6a in nsChromeRegistry::GetProfileRoot (this=0x81169e0, aFileURL=@0xbfe029d0) at nsChromeRegistry.cpp:1368 #6 0x40f38c8b in nsChromeRegistry::InitializeDataSource (this=0x81169e0, aPackage=@0xbfe02cac, aProvider=@0xbfe02cc4, aResult=0xbfe02cdc, aUseProfileOnly=0) at nsChromeRegistry.cpp:833 #7 0x40f37d86 in nsChromeRegistry::ConvertChromeURL (this=0x81169e0, aChromeURL=0x842ebd8) at nsChromeRegistry.cpp:638 #8 0x40f3efb1 in nsChromeProtocolHandler::NewChannel (this=0x81c5130, aVerb=0x40049dbc "load", aURI=0x842ea80, aLoadGroup=0x0, aNotificationCallbacks=0x0, aLoadAttributes=0, aOriginalURI=0x0, bufferSegmentSize=0, bufferMaxSize=0, aResult=0xbfe03038) at nsChromeProtocolHandler.cpp:547 #9 0x406ed3a8 in nsIOService::NewChannelFromURI (this=0x812b980, verb=0x40049dbc "load", aURI=0x842ea80, aGroup=0x0, notificationCallbacks=0x0, loadAttributes=0, originalURI=0x0, bufferSegmentSize=0, bufferMaxSize=0, result=0xbfe03038) at nsIOService.cpp:241 #10 0x400474d8 in NS_OpenURI (result=0xbfe03090, uri=0x842ea80, aGroup=0x0, capabilities=0x0, loadAttributes=0, bufferSegmentSize=0, bufferMaxSize=0) at ../../dist/include/nsNetUtil.h:79 #11 0x40fb65ef in NS_OpenURI (result=0xbfe0311c, uri=0x842ea80) at ../../../dist/include/nsNetUtil.h:98 #12 0x40fb4ae3 in nsStringBundle::OpenInputStream (this=0x842e9d8, aURLStr=@0xbfe030dc, in=@0xbfe0311c) at nsStringBundle.cpp:282 #13 0x40fb4a6e in nsStringBundle::GetInputStream (this=0x842e9d8, aURLSpec=0x40fa8ba0 "chrome://global/locale/brand.properties", aLocale=0x0, in=@0xbfe0311c) at nsStringBundle.cpp:209 #14 0x40fb4362 in nsStringBundle::nsStringBundle (this=0x842e9d8, aURLSpec=0x40fa8ba0 "chrome://global/locale/brand.properties", aLocale=0x0, aResult=0xbfe03148) at nsStringBundle.cpp:84 norris checked in shortly before shrike started a continuous orange streak about 36 hours ago.
Severity: normal → critical
Keywords: crash
I can't reproduce using either Windows or Linux. Pulling a fresh tree on Linux to see if I can see this. Just to be clear on the steps: I add the new prefs below, start the app, and load www.mozilla.org/quality/mailnews/APITest.html.
Status: NEW → ASSIGNED
Yes, I believe those are the right steps. If this still works for you, reassign to me and I will try tinderbox again.
Norris, did u see the output on the Console/Browser after loading the page? (Something like MAILNEWS TEST: Passed/Failed")
Yes, I got MAILNEWS TEST: Passed
Reassigning to mcafee.
Assignee: norris → mcafee
Status: ASSIGNED → NEW
Target Milestone: M14
This seems to be working for me, marking so.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
adding verifyme keyword.
Keywords: verifyme
this is pretty old now. I will mark verified. Do we still even have those tests as part of the smoketests?
Status: RESOLVED → VERIFIED
the test is checked in, but not used. We could never make it stable enough.
Product: Browser → Seamonkey
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.