Crash in [@ k7pswsen.dll | BaseThreadInitThunk] (K7 Total Security)
Categories
(External Software Affecting Firefox :: Other, defect)
Tracking
(firefox88 fixed)
Tracking | Status | |
---|---|---|
firefox88 | --- | fixed |
People
(Reporter: emilio, Assigned: toshi)
References
Details
(Keywords: crash)
Crash Data
Attachments
(2 files)
Looks like this DLL is blocklisted, but there are a few Nightly crashers.
Toshi, do you know how to proceed? Should we just update the blocklist entry for whatever DLL version is this?
Crash report: https://crash-stats.mozilla.org/report/index/2c470ebe-5fdc-4773-8b84-037c70210222
Reason: EXCEPTION_ACCESS_VIOLATION_WRITE
Top 8 frames of crashing thread:
0 k7pswsen.dll k7pswsen.dll@0x12346
1 k7pswsen.dll k7pswsen.dll@0x12283
2 kernel32.dll BaseThreadInitThunk
3 ntdll.dll _RtlUserThreadStart
4 kernelbase.dll TerminateProcessOnMemoryExhaustion
5 ntdll.dll wcstombs
6 ntdll.dll FinalExceptionHandlerPad17
7 k7pswsen.dll k7pswsen.dll@0x12283
Assignee | ||
Comment 1•4 years ago
|
||
Looking at the dumps, the current crash happens because k7pswsen.dll tried to hook PeekMessageW
by modifying an entry of xul.dll's Import Table though its memory attribute was read-only. It seems different from the previous problem bug 1339083, but given that we have blocked the module for years, it's safer to expand the version to be blocked.
I opened a support ticket PPPW-766741 here to let K7 Security know this problem. Hopefully they fix this issue in a future version.
Assignee | ||
Comment 2•4 years ago
|
||
Got the update on the ticket. They say their dev team is now looking into the case.
Assignee | ||
Comment 3•4 years ago
|
||
Assignee | ||
Comment 4•4 years ago
|
||
Comment 6•4 years ago
|
||
bugherder |
Description
•