Closed Bug 313585 Opened 20 years ago Closed 17 years ago

dwwin.exe causes ALL open instances of FF 1.07 browser windows to crash every time.

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

VERIFIED INVALID

People

(Reporter: dv8cowboy, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 I run XP Pro with AVG Firewall. At odd times a very quick message from the FW says 'malicious dwwin.exe' blocked, at which time All instances of FF crash immediately. Reproducible: Always Steps to Reproduce: 1.I have no idea where this dwin.exe comes from...the core browser, extentions I use or the AVG FW 2. 3. Not crashed
(In reply to comment #1) > See http://www.iamnotageek.com/a/dwwin.exe.php > I disabled error reporting, Thank you. We will see if this helps.Can the dwwin.exe be removed (and backed up somewhere? safely?- Thanks- Terry Mathis.Sounds like this should be a FF code writing fix also.
(In reply to comment #2) > I disabled error reporting, Thank you. We will see if this helps.Can the > dwwin.exe be removed (and backed up somewhere? safely?- Thanks- Terry > Mathis.Sounds like this should be a FF code writing fix also. > Don't remove or block it ! http://www.liutilities.com/products/wintaskspro/processlibrary/dwwin/
Depends what the location of the file is. If it's NOT \windows\system32\dwwin.exe it is probably spyware. Lots of spyware files are disguised as apparently legitimate windows files. C:\windows\system32\dwwin.exe is another application than C:\WINDOWS\dwwin.exe or C:\Program Files\dwwin.exe.
I am a Systems Security Analyst, my machine is ultra well protected, updated, and scanned frequently. Avast Pro, Black Ice, SpywareBlaster, SB Search and Destroy, Spyware Guard, a-squared, plus a few other goodies..dwwin.exe is where it is supposed to be. Still pointing at FF 1.07 Coding problem? Thanks for the input
reporter: please reinstall firefox and be sure to include talkback. then, hopefully when you crash, you'll get a series of dialogs from talkback, include your email address (it'll help people find your reports), then run talkback.exe and copy the incident id to this bug.
(In reply to comment #6) > reporter: please reinstall firefox and be sure to include talkback. then, > hopefully when you crash, you'll get a series of dialogs from talkback, include > your email address (it'll help people find your reports), then run talkback.exe > and copy the incident id to this bug. > - Already done, used workaround from reply #1, but still that won't fix the coding issue,so far dissing 'Error Reporting' AND in service.msc was a 'dirty fix'..I doubt that the crashes will continue. FF Coding? Thanks for all!- Terry
INVALID; not a Firefox bug.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg dwwin just means we crashed, but w/o a stack there's nothing we can do about it. when you dismiss their error reporter, the os of course closes us because we *crashed*. you can either get the .dmp file listed in the error report and analyze it w/ windbg, or attach w/ windbg directly and analyze the process crash directly. but dwwin causing the browser to close is not a bug, it's by design. note that there's only one *instance* of firefox, all windows share a common instance. this is also by design.
Resolution: INVALID → FIXED
Resolution: FIXED → INVALID
Status: RESOLVED → VERIFIED
Blocks: 619203
No longer blocks: 619203
You need to log in before you can comment on or make changes to this bug.