Closed
Bug 444099
Opened 16 years ago
Closed 16 years ago
comm-central SeaMonkey MailNews (3-pane) crashes easily
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: sgautherie, Unassigned)
References
Details
(Keywords: crash, regression)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1a1pre) Gecko/2008070706 SeaMonkey/2.0a1pre] (calemaisu-test-win32/1215437056) (W2Ksp4)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1a1pre) Gecko/2008070717 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4)
{{
MailNews crashes, with my usual profile, when trying to display:
*a News message.
*an IMAP Inbox folder.
*(or loading MN in "online" state, for that matter (I guess))
I submitted
fedd8570-4c70-11dd-9b82-001a4bd43ed6 08/07/2008 00:06
<http://crash-stats.mozilla.com/report/pending/fedd8570-4c70-11dd-9b82-001a4bd43ed6>
and
238f5447-4c71-11dd-b3e3-001a4bd43ed6 08/07/2008 00:07
<http://crash-stats.mozilla.com/report/pending/238f5447-4c71-11dd-b3e3-001a4bd43ed6>
but I'm not so sure they'll get out of "Your report is being processed"
state :-<
}}
KaiRo commented:
{{
Let's see - http://blog.mozilla.com/webdev/2008/07/07/socorro-delays/
}}
Flags: blocking-seamonkey2.0a1?
Comment 1•16 years ago
|
||
This bug is INVALID for now, as there is no source in comm-central yet. The calemaisu-test builds are just mere testing builds from a random state of development taken two weeks ago or so from CVS. The only non-obsolete part of those testing builds is the mozilla-central code pulled into them. Even the build system changes still are unreviewed.
Please reopen this is this still happens once we have switched to hg and have actual comm-central builds.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Updated•16 years ago
|
Flags: blocking-seamonkey2.0a1?
Reporter | ||
Comment 2•16 years ago
|
||
Agreed:
Yesterday, there were only tinderbox builds: I emailed you (only).
Today, I saw/tested it as a nightly: I assumed it was (already) becoming more "official".
(And, I assumed (all) the code was up to date. [Looking forward to it ;-)])
Anyway, this will be a warning to anyone else who would dare to try these builds ;->
V.Invalid
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 3•16 years ago
|
||
(In reply to comment #0)
> fedd8570-4c70-11dd-9b82-001a4bd43ed6 08/07/2008 00:06
> <http://crash-stats.mozilla.com/report/pending/fedd8570-4c70-11dd-9b82-001a4bd43ed6>
"NTDLL.DLL@0x7eeb / EXCEPTION_ACCESS_VIOLATION" but no useful details.
> 238f5447-4c71-11dd-b3e3-001a4bd43ed6 08/07/2008 00:07
> <http://crash-stats.mozilla.com/report/pending/238f5447-4c71-11dd-b3e3-001a4bd43ed6>
"NTDLL.DLL@0xf281 / EXCEPTION_ACCESS_VIOLATION" involving <mail.dll>...
*****
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1a1pre) Gecko/2008071215 SeaMonkey/2.0a1pre] (calemaisu-test-win32/1215900174) (W2Ksp4)
Anyway, no more crashes.
You need to log in
before you can comment on or make changes to this bug.
Description
•