134610 - core dump using version M18

Status: CLOSED INVALID

(SeaMonkey :: General, defect)

Description

[daniel]

There is not one sepecific incident where the browser with the mail open dumps
on me.

I hope the core dump will be ok

Comment 1

[daniel]

Attachment: core dump

Comment 2

[R.K.Aa.]

Is this some kind of joke?
The attachment is invalid, as far as i can tell. Please get a recent talkback
enabled build and provide talkback ID as well as steps to reproduce.

You may also wish to read the bug reporting guidelines found at 
http://www.mozilla.org/quality/bug-writing-guidelines.html

Quote:
"be sure that you've reproduced your bug using a build released within the past
three days"

M18 is far to old to report bugs against. Resolving as invalid.

Comment 3

[Andrew Lin]

rkaa-- while I agree that this bug is invalid, I don't think it's charitable to
be insulting the reporter like that.  For example, if I go directly to
ftp.mozilla.org (not an entirely unreasonable thing to do, no?) and look for
releases, I see (ftp://ftp.mozilla.org/):

m10/
m11/
m12/
m13/
m14/
m15/
m16/
m17/
m18/
m3/
m4/
m5/
m6/
m7/
m8/
m9/
[And then the more recent releases.]

If I wasn't paying close attention, I might very well assume that m18 is the
most recent available Mozilla.

Comment 4

[Andrew Lin]

argh, forgot to cc rkaa.  please see above comment

Comment 5

[daniel]

Your sarcasm is just great. Just the response someone wants when they have a
problem.

Comment 6

[Arthur]

Considering that it's the 1st of april I thought this was a joke too. :)

Comment 7

[Andrew Lin]

We may want to think seriously about restructuring that directory, so that it
has one folder latest/ and one folder older/ under which the old builds are
located.  I bet 99% of the people who end up there want the latest build.

Comment 8

[R.K.Aa.]

Andrew Lin: I'm sorry to have insulted anyone. I thought this bug was actually a
"troll", since not a single aspect of it is valid. I have decided to withdraw
from further Bugzilla activies since my comments are perceived as offending.
Thank you for pointing it out.

Reporter might still want to explain which format the core-dump is in.
Reopening.

Comment 9

[daniel]

it was supposed to have been a binary file, but I don't care anymore. I will
just deal with it.

Comment 10

[Christian :Biesinger (don't email me, ping me on IRC)]

looking at the stacktrace this is INVALID.
It's gzipped nonsense.

Comment 11

[Christian :Biesinger (don't email me, ping me on IRC)]

s/stacktrace/coredump/

Comment 12

[Ben Bucksch (:BenB)]

> Just the response someone wants when they have a problem.

Is bugzilla a support forum yet?

INVALID. Please grab a nightly, see Mozilla homepage.

Comment 13

[daniel]

jeesh you guys are jerks. I will find solution somewhere else, who needs this!

Comment 14

[Vadim Berezniker]

Nobody is trying to be a jerk.
You're overreacting.

If you're using debian, you should consider using something besides 'stable'
which has the M18 package. 

You must understand that mozilla has changed *significantly* from M18 to 0.9.9
A crash that affected M18 is most likely to be fixed in a newer build.