110307 - INVALID_POINTER error in chrome://.../history.js

Status: VERIFIED WORKSFORME

(Core Graveyard :: History: Global, defect)

Description

[Jim Avera]

Linux Build ID: 2001111506

The following errors are reported in the JavaScript Console
immediately after starting mozilla:

1. Error: redeclaration of const kIOServiceProgID
   Source File: chrome://commmunicator/content/utilityOverlay.js

2. Error: uncaught exception: [Exception... "Component returned failure code:
                   0x80004003 (NS_ERROR_INVALID_POINTER)
                   [nslPrefBranch.setCharPref]"
          nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"
          location:"JS frame ::
                            chrome://communicator/content/history/history.js 
                            :: GroupBy :: line 285"
          data:no]

Happens every time.

Comment 1

[Ashley Bischoff (blog at handcoding.com)]

Reporter: Have you tried a fresh profile? You can manage/create profiles with
"mozilla -profilemanager".

Comment 2

[Jim Avera]

The errors do not occur with a fresh profile.

What is in a profile which could provoke this kind of error?

If possible, mozilla should "clean out" corrupt information left behind
by previous aborted sessions, etc.

Comment 3

[Ashley Bischoff (blog at handcoding.com)]

Marking WFM as per reporter's comments.

Reporter: Sometimes cruft from very old profiles can "disrupt" current builds of
Mozilla. In a nutshell, the format of the settings file changes slightly over
time. And, occasionally, settings in the old format can confuse current builds.

At this point, you may be thinking that it'd be useful to be able to export the
settings from your old profile into your fresh profile -- unfortunately, that
functionality doesn't exist yet and is bug 22689.

Comment 4

[sairuh (rarely reading bugmail)]

mass-verifying WorksForMe bugs which haven't changed since 2001.12.31.

set your search string in mail to "EmperorLondoMollari" to filter out these
messages.