KALMUSI 0 Posted June 3, 2016 Share Posted June 3, 2016 It would be great to have a fix, but I am not aware of the designation "version 1254 of the internet module." I have V7 (7.0.325.1) on XP and V8 (8.0.312.0) on Windows 7. How does "version 1254 of the internet module" relate to these? On V7, if I click the button to check for updates, it offers V8. Does this include the fix? It seems not since I have the same problem on V8 in Win7. Please advise how I can get this fix. Thanks. Link to comment Share on other sites More sharing options...
SweX 871 Posted June 4, 2016 Share Posted June 4, 2016 With the version 1254 of the internet module, the problem look like fixed !!! I can confirm that - very nice to see it solved Link to comment Share on other sites More sharing options...
SweX 871 Posted June 4, 2016 Share Posted June 4, 2016 (edited) It would be great to have a fix, but I am not aware of the designation "version 1254 of the internet module." I have V7 (7.0.325.1) on XP and V8 (8.0.312.0) on Windows 7. How does "version 1254 of the internet module" relate to these? On V7, if I click the button to check for updates, it offers V8. Does this include the fix? It seems not since I have the same problem on V8 in Win7. Please advise how I can get this fix. Thanks. The button to check for updates in the GUI is for the product version itself and not the modules, the modules get's updated automatically together with the virus signature database. To check if you have "Internet protection module: 1254 (20160526)", you can for example click on your ESET tray icon and then click on About in the tray menu, then you find the module in the list to see your current one. Edited June 4, 2016 by SweX Link to comment Share on other sites More sharing options...
KALMUSI 0 Posted June 4, 2016 Share Posted June 4, 2016 I now see that I have an Internet Protection Module older than 1254. Thank you. Support is better when you don't assume that the person you are helping knows as much as you do. I am getting helped in tiny increments here, and I do appreciate it, but of course the next question is why don't I have 1254, and more important how to get it. Not being a nube, I figured out that I need to switch to the Pre-release update in Advanced Settings - Update Settings, and then do a virus signature database update. I now have 1254. I will test it and report back. Link to comment Share on other sites More sharing options...
KALMUSI 0 Posted June 5, 2016 Share Posted June 5, 2016 About 200 MB of files downloaded, and ekrn.exe is hovering around 117MB memory in use. This looks like problem solved. Thanks for the help! Link to comment Share on other sites More sharing options...
KALMUSI 0 Posted June 5, 2016 Share Posted June 5, 2016 Spoke too soon. With 3.1 GB downloaded, ekrn.exe is up to 589 MB. On it's way to failure. Time to shop for a new AV supplier. Link to comment Share on other sites More sharing options...
evvivame 0 Posted June 5, 2016 Share Posted June 5, 2016 Today i confirm again : solved with https://forum.eset.com/topic/8111-803191-for-years-everything-was-ok-and-memory-leak-come/?p=44873 Link to comment Share on other sites More sharing options...
SweX 871 Posted June 6, 2016 Share Posted June 6, 2016 Spoke too soon. With 3.1 GB downloaded, ekrn.exe is up to 589 MB. On it's way to failure. Time to shop for a new AV supplier. On XP or Win7 ? The fix (work around) included in IPM 1254 only applied for XP afaik. So the similar problem you have with Win7 is most likely not caused by the same bug that caused the issue in XP. You're free to change AV if you like, but if you want to see a solution, then working with ESET is your best option to solve it of course. Link to comment Share on other sites More sharing options...
KALMUSI 0 Posted June 10, 2016 Share Posted June 10, 2016 The problem is continuing on XP. I did not test Win 7 with the IPM 1254. Memory use by ekrn.exe seems to grow at a slower rate, but it is growing, so I feel the issue has been made less intrusive, but it is not fixed. The link given above with the statement "Today i confirm again : solved with https://forum.eset.c...k-come/?p=44873" is simply page one of this same thread, so no fix is "confirmed." Link to comment Share on other sites More sharing options...
SweX 871 Posted June 11, 2016 Share Posted June 11, 2016 The problem is continuing on XP. I did not test Win 7 with the IPM 1254. Memory use by ekrn.exe seems to grow at a slower rate, but it is growing, so I feel the issue has been made less intrusive, but it is not fixed. The link given above with the statement "Today i confirm again : solved with https://forum.eset.c...k-come/?p=44873" is simply page one of this same thread, so no fix is "confirmed." Hmmm. All I can say is that I can't reproduce the leak/high ram usage anymore on XP, even doing the same things which would make the ram usage rocket earlier, it doesn't do that anymore and the ram usage stays at the same level as it is at boot. No, that link goes to a forum post (#18) which links to a KB article explaining how to enabled/disabled pre-release updates, I assume evvivame enabled PR updates i order to get IPM 1254 which in return fixed the issue for him/her, and wanted to confirm it. Well, also test Win 7 to see if there's any improvement/worse/difference at all. Link to comment Share on other sites More sharing options...
KALMUSI 0 Posted June 16, 2016 Share Posted June 16, 2016 (edited) 330 MB of files downloaded today, and ekrn.exe seems to be hovering at 140MB RAM used. Seems to be working OK. The Internet protection module: 1255 (20160601) arrived without the need to switch to "Pre-release" updates. I'm going to stop thinking about this - at least until the problem comers back. (Hopefully that is an "if.") Well done ESET. I hope my faith is restored. Edited June 16, 2016 by KALMUSI Link to comment Share on other sites More sharing options...
Recommended Posts