Closed Bug 109658 Opened 23 years ago Closed 14 years ago

TAB widgets are not displayed in 64bit builds

Categories

(SeaMonkey :: Tabbed Browser, defect)

Sun
Solaris
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: roland.mainz, Unassigned)

Details

(Keywords: 64bit)

2001-11-10-cvs sparcv9 build on Solaris 2.7 SPARC.
Pressing CTRL-T seems to create a new blank browser TAB - but the widgets to
switch between the TABs.

Log prints the following error:
-- snip --
WEBSHELL+ = 6
xxlib_find_handle: 'xxlib-default' entry 1001ed1d0
###!!! ASSERTION: AddObserver: trying weak object that doesnt support
nsIWeakReference: 'weakRefFactory', file
../../../../../../../home/mozilla/src/2001-11-10-cvs/mozilla/xpcom/ds/nsObserverList.cpp,
line 78
###!!! Break: at file
../../../../../../../home/mozilla/src/2001-11-10-cvs/mozilla/xpcom/ds/nsObserverList.cpp,
line 78
************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE)
[nsIObserverService.addObserver]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)" 
location: "JS frame :: chrome://communicator/content/utilityOverlay.js ::
utilityOnLoad :: line 406"  data: no]
************************************************************
-- snip --
This issue was already present in 0.9.5 milestone... ;-(
Keywords: 64bit
spam: set your filter for "SeverusSnape" to avoid the influx of bugmail

changing QA contact of open tabbed browser bugs from blake to me. if this bug
requires a reassignment, however, feel free to change it!
QA Contact: blakeross → sairuh
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1
Reassigning to new component owner.
Assignee: hyatt → jaggernaut
Status: ASSIGNED → NEW
QA Contact: sairuh → pmac
Tabs are working correctly in AIX trunk builds after fixing the xptcinvoke code
as described in Bug 178499. A similar fix needs to be made for Solaris.
retargeting
Target Milestone: mozilla1.1alpha → Future
is this bug still valid?
Product: Core → SeaMonkey
Assignee: jag → nobody
QA Contact: pmac → tabbed-browser
Target Milestone: Future → ---
(In reply to comment #6)
> is this bug still valid?

Not that I know of.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.