279604 - Total crashes after journal links in pubmed abstracts [@ @0x00?????? destroyTimerEvent ]

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Niels]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 MultiZilla/1.7.0.1a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 MultiZilla/1.7.0.1a

The pubmed medline search engine displays clickable images that link to the
journal's article page.
Sometimes Mozilla completely crashes after clicking these images. I have
experienced this behaviour for more than a year now. The link targets are
similar to
http://www.ncbi.nlm.nih.gov/entrez/utils/lofref.fcgi?PrId=3058&uid=15662727&db=pubmed&url=http://dx.doi.org/10.1002/cm.20052
and probably involve (multiple?) redirects.

I have't checked this without Multizilla or under FireFox. It crashes only
sometimes and has never happened with the first click onto these links.

Reproducible: Sometimes

Steps to Reproduce:
1. to see these image links go to http://www.ncbi.nlm.nih.gov/entrez/query.fcgi
2. search for e.g. "cell"
3. on the results page chose "Abstract" and click the "Display" button
4. do some more searches in multiple tabs, click the journal links from time to
time and wait for the crash. It only happens sometimes, never with the first click.




Talkback Incident IDs: TB3258174W, TB3255300E. Will check the next time and
report the module.

Comment 1

[Stephen Donner [:stephend] Not actively reading bugmail]

BTW, in the future you can look these up at http://talkback-public.mozilla.org

0x006f0042
destroyTimerEvent 
[d:/BUILDS/tinderbox/Mozilla1.7/WINNT_5.0_Clobber/mozilla/xpcom/threads/nsTimerImpl.cpp,
line 456]
PL_DestroyEvent 
[d:/BUILDS/tinderbox/Mozilla1.7/WINNT_5.0_Clobber/mozilla/xpcom/threads/plevent.c,
line 713]
PL_HandleEvent 
[d:/BUILDS/tinderbox/Mozilla1.7/WINNT_5.0_Clobber/mozilla/xpcom/threads/plevent.c,
line 686]
PL_ProcessPendingEvents 
[d:/BUILDS/tinderbox/Mozilla1.7/WINNT_5.0_Clobber/mozilla/xpcom/threads/plevent.c,
line 612]
nsEventQueueImpl::ProcessPendingEvents 
[d:/BUILDS/tinderbox/Mozilla1.7/WINNT_5.0_Clobber/mozilla/xpcom/threads/nsEventQueue.cpp,
line 402]

Comment 2

[Boris Zbarsky [:bzbarsky]]

I can't seem to reproduce on Linux...  a testcase that shows the problem would
be very nice (as always).  :(

Comment 3

[Niels]

Same problem, new talkback IDs: TB3841820Y, TB3837392M (sorry, the Module fields
are empty on the talkback pages!?) Unfortunately it is not really reproducible
as it happens very irregularly. Often it works fine for days and then  it
happens several times a day. 

Comment 4

[Andrew Schultz]

can you try without multizilla?

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.