Closed
Bug 680814
Opened 14 years ago
Closed 14 years ago
Seamonkey "find in this page" freezes on ASUS G73JH
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mmikeda, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110813 Firefox/6.0 SeaMonkey/2.3
Build ID: 20110813174900
Steps to reproduce:
Using Asus G73jh notebook, Operating system Windows 7 64 bit. Browser Seamonkey 2.3 (also happened under Seamonkey 2.2).
Choose "Find In This Page" option in Edit menu.
Entered text in the "Find" box that is not on web page.
Actual results:
Entire system froze. Only way to unfreeze was to turn power switch off.
This happens every time I enter text in "Find" box that is not on web page.
Expected results:
Browser should have just indicated text was not on webpage.
Comment 1•14 years ago
|
||
A system freeze is always the fault of a driver, hardware or the system itself.
Seamonkey is a usermode application and a usermode applications can't freeze the os. SM can however trigger a bug in a driver.
I would try to upgrade the graphic card driver from the manufacture homepage (AMD,nvidia, intel).
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Thanks for the help.
Updated the ATI Mobility Radeon video driver and the Realtek HD Audio driver. The problem seems to have been fixed, at least it hasn't occurred the several times that I've tested for it.
Interestingly enough, it seems to have been the update to the Realtek driver that fixed the problem.(In reply to Matthias Versen (Matti) from comment #1)
> A system freeze is always the fault of a driver, hardware or the system
> itself.
> Seamonkey is a usermode application and a usermode applications can't freeze
> the os. SM can however trigger a bug in a driver.
>
> I would try to upgrade the graphic card driver from the manufacture homepage
> (AMD,nvidia, intel).
Comment 3•14 years ago
|
||
Great that you found a way to fix the issue.
System freezes are difficult for us because it can't be our problem and we can't help much to resolve it.
You need to log in
before you can comment on or make changes to this bug.
Description
•