Closed Bug 287225 Opened 20 years ago Closed 19 years ago

Crash after some time of inactivity [@ nsSHTransaction::Release ]

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: miha, Unassigned)

Details

(Keywords: crash)

Crash Data

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

After I leave computer for some time and come back later (several hours) and try
to use Mozilla, it crashes. Sometimes it crashes just by restoring a window,
sometimes when I start writing into address bar and sometimes when I try to read
a new mail message that has arrived.

Reproducible: Sometimes

Steps to Reproduce:
1. Start and use Mozilla.
2. Stop using computer.
3. Try to use Mozilla after some hours of computer inactivity.

Actual Results:  
Mozilla crashes and Talkback starts.

Expected Results:  
Stay up and running.

Mozilla crashes in different modules, not always in the same one. Some Talkback
crash IDs:
TB4457727Y
TB4481631H
TB4493223M
TB4493223M

Sometimes, but not always, after a crash Mozilla can't be run anymore and
produces an istant crash. Talkback IDs of this:
TB4481637Z
TB4481647Y
TB4481652Y

Sometimes it helps if I run another version of Mozilla (I have installed several
versions). Mozilla then starts and works OK.

This bug is also happening with 1.8b1.
Stacktraces for incidents are different, unique signatures are:
1x nsCOMPtr_base::assign_with_AddRef 
4x nsSHTransaction::Release (whole TB db has 5 incidents)
2x nsBoxFrame::PaintChild
Keywords: crash
Summary: Crash after some time of inactivity → Crash after some time of inactivity [@ nsSHTransaction::Release ]
Version: unspecified → Trunk
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Crash Signature: [@ nsSHTransaction::Release ]
You need to log in before you can comment on or make changes to this bug.