Closed Bug 506257 Opened 16 years ago Closed 16 years ago

Keeping Space pressed makes SM crash [@ nsNntpCacheStreamListener::OnStartRequest]

Categories

(SeaMonkey :: MailNews: General, defect)

Product:
SeaMonkey
Component:
MailNews: General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 130442

People

(Reporter: stefan.blumenrath, Unassigned)

Details

(Keywords: crash)

Crash Data

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.1pre) Gecko/20090717 SeaMonkey/2.0b1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.1pre) Gecko/20090717 SeaMonkey/2.0b1 SM crashes reproducable if I switch through the news pressing Space for about 10-20 seconds. Reproducible: Always Steps to Reproduce: 1. Display any posting. 2. Press Space for switching to the next message, not giving SM the time to load the message from the server nor to display it. 3. Hold Space for a while Actual Results: SM Crashes, Crashreporter starts Expected Results: Not that :-)
Please add the Breakpad Crash-IDs here. You can find them type "about:crashes" into the Urlbar. Please copy the IDs here with an leading "bp-"[ID] to give an funktional Url to the report.
Version: unspecified → Trunk
Keywords: crash
Summary: Keeping Space pressed makes SM crash → Keeping Space pressed makes SM crash (@nsNntpCacheStreamListener::OnStartRequest)
The line we're crashing in is http://hg.mozilla.org/comm-central/annotate/413ab70abcfb/mailnews/news/src/nsNNTPProtocol.cpp#l680 This hasn't been changed in a long time, interestingly.
related to or possibly the same as bug 130442, perhaps?
From looking at stacks from there, this is a dupe, yes.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Summary: Keeping Space pressed makes SM crash (@nsNntpCacheStreamListener::OnStartRequest) → Keeping Space pressed makes SM crash [@ nsNntpCacheStreamListener::OnStartRequest]
Crash Signature: [@ nsNntpCacheStreamListener::OnStartRequest]
You need to log in before you can comment on or make changes to this bug.