Closed Bug 988489 Opened 8 years ago Closed 7 years ago
hangs when cache file is deleted (by Symantec Endpoint Protection)
hangs every time 31.0a1 (2014-03-20) build https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uact=8&ved=0CDAQFjAB&url=https%3A%2F%2Fwww.vmware.com%2Fsupport%2Fvsphere5%2Fdoc%2Fvsphere-esx-vcenter-server-51-release-notes.html&ei=cQMzU_n7OsPjsASFtIL4Aw&usg=AFQjCNHj3fjQf_wVl3RzNROGyzHYUsJ6NQ&sig2=1h6eivfeOcpXjEUkIXDXQQ
Attachment #8397288 - Attachment description: windbg stacktrace js::jit::DoTypeMonitorFallback → windbg stacktrace mozjs!js::jit::NameIC::update
the page load doesn't fail in IE Next, will try more recent nightly build
Symantec Endpoint is catching what it thinks is badness in cache and deleting cache file(s). Scan type: Auto-Protect Scan Event: Risk Found! Security risk detected: IFrame.Exploit File: C:\Users\wsm0.AD\AppData\Local\Mozilla\Firefox\Profiles\a3cv86if.default\cache2\entries\EF7B476F3146C47258EB07A69305843B106A7405 Location: C:\Users\wsm0.AD\AppData\Local\Mozilla\Firefox\Profiles\a3cv86if.default\cache2\entries Computer: WSM0-I7 User: wsm0 Action taken: Pending Side Effects Analysis : Access denied Date found: Wednesday, March 26, 2014 3:16:20 PM link resolves to https://www.vmware.com/support/vsphere5/doc/vsphere-esx-vcenter-server-51-release-notes.html
followed by Security Risk Found!IFrame.Exploit in File: C:\Users\wsm0.AD\AppData\Local\Mozilla\Firefox\Profiles\a3cv86if.default\cache2\entries\EF7B476F3146C47258EB07A69305843B106A7405 by: Auto-Protect scan. Action: Cleaned by Deletion. Action Description: The file was deleted successfully.
Wayne: if you disable Symantec Endpoint Protection, can you load the page? Is this a regression in Nightly 31?
Summary: hang js::jit:: → Symantec Endpoint Protection hang
(In reply to Chris Peterson (:cpeterson) from comment #4) > Wayne: if you disable Symantec Endpoint Protection, can you load the page? Yes. I excluded the cache directory from Norton scanning and the problem went away. > Is this a regression in Nightly 31? I have no data to say it is a regression or not. Nor have I checked any other builds or releases. If needed, I will do so Perhaps related to that ... my question is should firefox not crash if a cache file is unexpectedly missing?
if a cache file is unexpectedly missing, what should be expected behavior?
Summary: Symantec Endpoint Protection hang → hangs when cache file is deleted (by Symantec Endpoint Protection)
Expected behavior is to load the resource from the network, but right now there is a bug and such resource fails to load. Bug 913812 should fix this. Anyway, I don't understand what exactly happens in your case. Application really should not hang and I don't see any hang in the stack traces. In comment #5, you write something about crash, so I'm confused. Btw. did you turn on the new cache backend manually?
Depends on: 913812
I've reproduced it locally and the code asserts in mozilla::net::CacheFileChunk::BufForReading().
(In reply to Michal Novotny (:michal) from comment #7) > Anyway, I don't understand what exactly happens in your case. Application > really should not hang and I don't see any hang in the stack traces. In > comment #5, you write something about crash, so I'm confused. My mistake - replace all references to crash with the word "hang" > did you turn on the new cache backend manually? yes
Tracking for enable, hang seems serious.
Wayne, any news here? We are soon going to enable by default. If this is no longer a problem or is just occasional I will close or postpone.
I'll give an update on Tuesday - I'll have to update my work PC and re-enable scanning, plus I'm not in work much the next few days.
I won't get to this til later in week
Wayne, I'll take the liberty to assign this to you to confirm the bug is there or is fixed. Thanks.
Assignee: nobody → vseerror
Honza, Michal, thanks for the fixes. Something changed such that symantec scan didn't delete cache files. But using current nightly I couldn't cause this by randomly and also massively deleting cache files. WFM
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.