Closed
Bug 328794
Opened 19 years ago
Closed 15 years ago
yahoo mail beta crash [@ nsXPConnect::ReleaseJSContext]
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: ratan.work, Unassigned)
Details
(Keywords: crash, qawanted, topcrash-)
Crash Data
Attachments
(1 file)
20.54 KB,
text/plain; charset=utf-8
|
Details |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; yie6; SV1; .NET CLR 1.1.4322)
Build Identifier: Firefox15
Talkback ids:
=============
1. nsXPConnect::ReleaseJSContext 4da03fad
http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=15486469
2. nsXPConnect::ReleaseJSContext 4da03fad
http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=15299938
Similar to bug:
http://bugzilla.mozilla.org/show_bug.cgi?id=316114
Creating a back to track from talkback ids.
among top 10 crashers (nsXPConnect::ReleaseJSContext 1.15% 2461)
FF 1.5.0.1
Reproducible: Sometimes
Updated•19 years ago
|
Component: General → Build Config
Product: Firefox → Core
Version: unspecified → 1.0 Branch
Updated•19 years ago
|
Component: Build Config → XPConnect
Comment 1•19 years ago
|
||
Dupe.
Reporter, if you feel this was done in error, please REOPEN.
Robin Monks
I ♥ BugSpam
*** This bug has been marked as a duplicate of 328787 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Very very different stack; reopening. This crash also occurs on other AJAX-y sites.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Also similar to bug 305181 (in addition to bug 316114 mentioned above), but those are both fixed for 1.5; this is a topcrash in 1.5.0.1.
This is an analysis of the raw stack dump from talkback (along with talkback's info) of an occurrence of this crash. Talkback mangles the top few frames; they do make sense in the raw data.
Flags: blocking1.8.0.3?
Is the Yahoo! Mail Beta something that's open to the public, or do I need some special way to test it?
Updated•19 years ago
|
Flags: blocking1.8.0.3? → blocking1.8.0.3+
Comment 6•19 years ago
|
||
(In reply to comment #5)
> Is the Yahoo! Mail Beta something that's open to the public, or do I need some
> special way to test it?
Send me your yahoo id and I'll get you access.
-- Jeremy
Comment 7•19 years ago
|
||
There isn't enough time to get a patch baked before the 1.8.0.4 dev freeze, and it doesn't look like there's any progress. Moving out a release.
Flags: blocking1.8.0.5?
Flags: blocking1.8.0.4-
Flags: blocking1.8.0.4+
Updated•19 years ago
|
Assignee: nobody → dbradley
QA Contact: general → xpconnect
Comment 8•19 years ago
|
||
I have not seen any crashes with more recent builds of SeaMonkey. I don't know if this is because of changes in SeaMonkey or changes in Yahoo! Mail Beta.
Comment 9•19 years ago
|
||
Not going to make 1.8.0.5 since we don't have a patch, no way to reproduce this, and there are only 20 incidents in Firefox 1.5.0.4 Talkback data (out of a 10 day sample of ~26,000 incidents).
Adding qawanted keyword to see if people can try to reproduce this with recent nightlies or Firefox 1.5.0.4. If we can find a fix for this, we can consider it for the 1.8.1 branch and then maybe a future 1.8.0 release.
Comment 10•19 years ago
|
||
Until we get better confirmation that this issue still exists (and is reproducible) taking it off the radar for 1.8.1
Flags: blocking1.8.1? → blocking1.8.1-
Comment 11•19 years ago
|
||
I got this same stack running the Beta1 on Windows the other day - here is my talkback id - http://talkback-reports.mozilla.org/search/private.jsp?search=2&type=iid&id=20828875. My crash occurred when the machine was idle and I was not running the Yahoo beta mail, but may have had something ajaxy running.
Comment 12•19 years ago
|
||
I received a similar stack when testing the beta1 build the other day - http://talkback-public.mozilla.org/search/start.jsp?search=2&type=iid&id=20828875. Although I did not have Yahoo mail beta running, I may have had some other ajaxy application up. This happened after the Windows machine had been idle overnight.
Updated•18 years ago
|
Assignee: dbradley → nobody
Comment 13•18 years ago
|
||
bug reporter,
if you have yahoo messenger installed, try the new version 8.1 http://messenger.yahoo.com/ which is reported in bug 322363.
If your problem goes away then close your bug as a duplicate of bug 322363.
Comment 14•17 years ago
|
||
Marcia do you still see this?
Ratan writes "been running Yahoo Messenger version 8.1.0.413 and FF Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 and haven't seen these crashes. However, I don't have Yahoo toolbar installed"
Still common on talkback. Eg. TB34743573 "I was spell checking a new email within the email site and as soon as I try the spell check it crashes." TB34738355 also has comments.
Certainly reproducible for some people out there ... Google maps frequently mentioned, eg TB34681271, but stack trace is different Other examples TB34666593, TB34695441 - file a new bug?? (no other bugs filed with this same top of stack nsXPConnect::ReleaseJSContext)
Comment 15•17 years ago
|
||
I no longer can get to my Yahoo Mail using my Mozilla FireFox Browser.
When I click on Yahoo Mail, I get the following errors:
"The page isn't redirecting properly."
"Firefox has detected that the server is redirecting the request for this address in a way that will never complete."
This was coincidental with 2 events:
1. "I upgraded to FireFox 2.0.0.13"
2. "I downloaded Apple SAFARI"
Before I read this page I was blaming Apple for the problem.
At least I can check my Yahoo Mail on SAFARI.
I hope FireFox fixes this (so I can brag it up again).
Comment 16•17 years ago
|
||
Don, I seriously doubt that what you're seeing is related to this bug report.
Comment 17•15 years ago
|
||
Sounds like dbaron got about as far as possible with the Talkback data.
Status: NEW → RESOLVED
Closed: 19 years ago → 15 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•14 years ago
|
Crash Signature: [@ nsXPConnect::ReleaseJSContext]
You need to log in
before you can comment on or make changes to this bug.
Description
•