Closed Bug 825600 Opened 12 years ago Closed 6 years ago

Startup crash in lmrn.dll

Categories

(Firefox :: General, defect)

18 Branch
x86
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox18 --- affected
firefox19 --- affected

People

(Reporter: kairo, Unassigned)

Details

(Keywords: crash, Whiteboard: [startupcrash])

Crash Data

This bug was filed from the Socorro interface and is report bp-5b8cf8e9-c1af-4872-9a7d-f2f692121231 . ============================================================= Crash Reason: Unhandled C++ Exception Top frames: 0 KERNELBASE.dll RaiseException 1 msvcr100.dll _CxxThrowException f:\dd\vctools\crt_bld\self_x86\crt\prebuild\eh\throw.cpp:155 2 lmrn.dll lmrn.dll@0x3146 3 lmrn.dll lmrn.dll@0x6dcf 4 lmrn.dll lmrn.dll@0x89d2 5 lmrn.dll lmrn.dll@0xaf34 6 kernel32.dll ReadFileImplementation 7 nspr4.dll FileRead nsprpub/pr/src/io/prfile.c:42 8 xul.dll nsFileStreamBase::Read netwerk/base/src/nsFileStreams.cpp:174 9 xul.dll nsFileInputStream::Read netwerk/base/src/nsFileStreams.cpp:430 10 xul.dll mozilla::openPrefFile modules/libpref/src/Preferences.cpp:772 11 xul.dll mozilla::Preferences::ReadAndOwnUserPrefFile modules/libpref/src/Preferences.cpp:624 This is rising in the last few days on 17 and 18 at least, present across all kinds of versions as you can see in the signature summary of https://crash-stats.mozilla.com/report/list?signature=lmrn.dll%400x3146 It's not a top crash yet, but definitely fast-rising. I have no clue where this DLL belongs, and Google also doesn't seem to have heard of it (yet).
I bet that this is some kind of malware. Could you ask a beta user by email or is the email address not collected anymore ?
I looked around on the web and I couldn't find much about that particular dll.
(In reply to Matthias Versen [:Matti] from comment #1) > I bet that this is some kind of malware. How do you get to that assessment? Just because the DLL name wasn't know until this crash came up? That's pretty weak evidence. This crash continues rising on multiple channels including 17 release and 18 beta, now #32 in 18.0b7 and #50 on 17.0.1 (but #22 yesterday).
It belongs to a jmdp folder: http://systemexplorer.net/file-database/file/lmrn-dll Almost all comments are in Spanish. Maybe it's a program (screensaver?) related to Juan Martin Del Potro, the tennisman.
OS: Windows NT → Windows 7
Whiteboard: [startupcrash]
Crash Signature: [@ lmrn.dll@0x3146] → [@ lmrn.dll@0x3146] [@ _invalid_parameter_noinfo]
With combined signatures, it's #29 top browser crasher in 18.0.1. lmrn.dll usually comes bundled with stij.exe in the same C:\Windows\SysWOW64\jmdp directory. stij.exe belongs to Perion Network Ltd., the developer of IncrediMail and Smilebox.
Crash Signature: [@ lmrn.dll@0x3146] [@ _invalid_parameter_noinfo] → [@ lmrn.dll@0x3146] [@ lmrn.dll@0x3147] [@ _invalid_parameter_noinfo]
Version: unspecified → 18 Branch
(In reply to Scoobidiver from comment #6) > ... belongs to Perion Network Ltd., > the developer of IncrediMail and Smilebox. That's really good info, how did you find that out? Is this part of IncrediMail, then? I guess that might be a somewhat popular piece of software, which could explain why this has been rising.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #7) > That's really good info, how did you find that out? As explained in comment 6, if you search lmrn.dll on Internet, you find scanning logs and stij.exe in the same repository. This DLL is known to belongs to Perion (see http://systemexplorer.net/file-database/file/stij-exe), developer of IncrediMail (see https://en.wikipedia.org/wiki/Perion_Network).
(In reply to Scoobidiver from comment #8) > As explained in comment 6, if you search lmrn.dll on Internet, you find > scanning logs and stij.exe in the same repository. Well, when I filed the bug a month ago, it wasn't found anywhere yet. Good that it now is and we know more about it.
Don't currently see any examples
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.