You can add me as another data point for just had my first kernel panic crash due to 'esets_proxy' — I've got ESET Cyber Security 6.0.9.1 installed & current on my late '11 MacBook Pro, and installing yesterday's OS X Update 10.9.3 seems to have kicked it over into being a problem; I would occasionally see little bursts of high CPU activity that seemed to be associated with ESETS before that, but not to the point where it would cause system-level problems. However, when my computer was rebooting after the system update installation yesterday, I got a gray screen flashing over my desktop after logging in that I had to manually shut down my laptop to escape, and I strongly suspect this morning's kernel panic crash means that problem yesterday was also likely caused by an issue with ESETS.
Very frustrating + disconcerting; have filed a Customer Care support request, but seeing that this has been an issue for people going as far back as a year ago does not fill me with confidence that it will be fixed promptly now.
