Closed Bug 2667 Opened 26 years ago Closed 26 years ago

Crash typing '*' to expand bottom NNTP server in folder pane

Categories

(MailNews Core :: Backend, defect, P2)

x86
Windows NT

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: lchiang, Assigned: bugz)

Details

<initial description taken from bugsplat 336154> See the talkback report for a stack trace ------- Additional Comments From phil 11/30/98 08:35 ------- Subject: Pressing * on Last News Server Causes Crash Date: Fri, 20 Nov 1998 19:42:32 -0500 From: Kevin Hecht <khecht19@idt.net> Organization: Villanova University Newsgroups: netscape.champions.beta, netscape.champions 4.5 Final Build 98293 on Windows NT Server 4.0 Build 1381 (Service Pack 4) running on a P5-166/128MB RAM. MS Visual C++ 6.0 Service Pack 1 Debug DLLs installed. Pressing the * key to expand the subscribed newsgroups list on the last news server in the list causes a crash. To reproduce: 1. In the Message Center or left Messenger pane, highlight the last news server in the list. 2. Press the * to expand the subscribed groups. 3. Netscape crashes. This does not affect any other news servers in the list - only the last one. This report is based on several in netscape.communicator and can be confirmed on several machines here. See the Dr. Watson crash log below and Talkback event KTT25PGZ for more. -- Kevin Hecht
Talkback incident ID is 1549477
Setting all current Open Critical and Major to M3
Assignee: mscott → marek
If this is going to get fixed for 4.51, marek has to assign someone to it. The crash shows that it dies in old libmsg tree expand/collapse code, and since 5.0 is chucking all that old tree code in favor of RDF and the XPFE tree control, there's no point in keeping this bug open for 5.0.
Status: NEW → RESOLVED
Closed: 26 years ago
QA Contact: 4080
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
Ok, I will mark this bugzilla bug as "invalid" then and go and reopen the bugsplat 336154 bug.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.