84977 - News can't open one of my newsgroups (INVALID_POINTER error)

Status: VERIFIED FIXED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Skewer]

Procedure: Difficult to reproduce procedure, this somehow occurred after weeks
of use. Tried to load newsgroup alt.html, have two news accounts.

Expected: Newsgroup opens.

Actual: Newsgroup doesn't open. This pops into my JS console:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgFolder.getMsgDatabase]"  nsresult:
"0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame ::
chrome://messenger/content/commandglue.js :: ChangeFolderByDOMNode :: line 118"
 data: no]
Source File: 
Line: 7

Build: 2001060804 Win98. This has happened in previous builds.

Comment 1

[Håkan Waara]

This is a duplicate. (Bienvenu, we chatted in that bug, remember?)

Comment 2

[David :Bienvenu]

looks like the db might have been corrupted...do you ever run two versions of
the client against the same profile?

Comment 3

[Skewer]

I think the database corruption may have something to do with my frequent
encounters of bug 83486.

Comment 4

[David :Bienvenu]

No, I don't think so. bug 83486 has to do with partial, incomplete messages
getting into the memory cache and has nothing to do with the database.

Comment 5

[Skewer]

Temporary, horrible workaround: Unsubscribe and resubscribe to the faulty newsgroup.

Comment 6

[David :Bienvenu]

I'll fix the handling of the corrupted database, though I don't know the cause
of the corruption (other than running two clients against the same profile).

Comment 7

[dave.close]

As I reported in bug 85920, I had a similar problem. However, the suggested
workaround of unsubscribing was not useable. Merely selecting the problem group
was enough to crash Mozilla. Fortunately, stephend suggested deleting the msf
files, and that, along with deleting the rc file, seems to have cured the
problem. As he suspected, I've upgraded Mozilla from version to version without
making any change to the profile.

Comment 8

[David :Bienvenu]

you can unsubscribe without selecting the newsgroup by using the subscribe UI,
which is what Stephen meant, I believe. Unsubscribing merely deletes the .msf file

Comment 9

[[e-mail] (gone - use [e-mail] instead)]

I should note that I've seen the crash myself, but only at work (after one day 
running Moz with Netscape 6.1 concurrently, and they're sharing the same 
profile).  I believe it's safe to say that since I haven't seen this crash on my 
home machine which uses only the latest Moz trunk builds, that this is a cause 
of the bug.

Comment 10

[dave.close]

Perhaps it is a form of data base corruption. But my environment does not use
any browser except Mozilla. I started with Msomething, then went through 0.7 to
0.9.1 with a few non-release builds scattered in there.

Would there be value in looking at my old msf file? I've saved a copy.

Comment 11

[scottputterman]

moving to 0.9.3

Comment 12

[David :Bienvenu]

I checked in code to the trunk so we shouldn't get that js assertion anymore,
and if we have a corrupted .msf file, we should just redownload all the headers
again. If you have a test case, please try it out and let me know if it works.
Thanks.

Comment 13

[David :Bienvenu]

marking fixed - please reopen if you see this again (only fixed on the trunk,
not the branch)

Comment 14

[[e-mail] (gone - use [e-mail] instead)]

Skewer, do you see this at all anymore?  I don't see it with my trunk build 
(2001-06-29-04) on Windows 2000.

Comment 15

[Skewer]

I will reopen this if I get any more corruption problems. Currently my profile
is stored in a Windows folder away from Netscape (in fact NS6.01 is completely
gone) so if anything happens Netscape won't be the cause.

Comment 16

[[e-mail] (gone - use [e-mail] instead)]

I haven't seen this at home with an old profile, nor with a newly created
profile (and I have Netscape 6.1 PR1 running alongside moz).  Verifying with
build 2001-07-10-09.  We should refile this if we see it again, but like I said,
I haven't.