PDA

View Full Version : ESS Firewall - Interactive Mode hangs egui.exe


techcafe
February 9th, 2008, 06:24 PM
anyone else experiencing problems with the firewall in interactive mode? specifically, in my case, when creating/modifying firewall rules, either manually or via the firewall's popup (interactive) dialog, the ESS GUI (egui.exe) will hang with the ESS GUI and/or interactive dialog stuck on the screen, unresponsive to input. the only way to recover is to kill the egui.exe process via task manager and restart it manually. of course, the same behaviour repeats itself some moments later if/when the firewall rules are manually edited again, either via the rules editor or an interactive dialog.

imo, ESS needs to go into the shop for repairs.

Marcos
February 10th, 2008, 02:47 AM
The fact that one encounters a problem doesn't make it a general problem that occurs on every computer. Personally I haven't heard about the one you've encountered even though millions of people have already installed v3 and haven't reported it. Couldn't it be that a firewall window just doesn't show up on top? Does it happen for every rule you create, regardless of the application?

techcafe
February 10th, 2008, 03:47 PM
-{ Quote: "The fact that one encounters a problem doesn't make it a general problem that occurs on every computer. Personally I haven't heard about the one you've encountered even though millions of people have already installed v3 and haven't reported it. Couldn't it be that a firewall window just doesn't show up on top? Does it happen for every rule you create, regardless of the application?" }-

here are the details of the egui issue i'm experiencing (i also sent this to eset today):

below is the egui.exe error that is reported in the Application log:

so far, i've noticed that the crash only occurs after pressing the [Apply] button (when making changes in the firewall rules editor). if the [OK] button is pressed (instead of Apply), the rules editor (egui.exe) does not crash. however, the point of using Apply (instead of OK) is that changes get applied without having to close and re-open the rules editor. to prevent egui.exe from crashing, i've stopped using the Apply button, and press OK instead (and re-open the editor if i've got more changes to make). i should also mention, egui does not always crash when the Apply button is pressed, it's an intermittent/random problem/bug. it hasn't crashed (so far) when i press OK instead of Apply.

also, egui will (occasionally) generate an error message (see attached screen capture) that says an unsupported operation was attempted. i've seen that error message a few times so far; each time, the firewall was in interactive mode, i was making changes in the rules editor AND a firewall (allow/deny) notification had popped-up on the screen. when i attempted to respond to the firewall notification (attempting to press allow or deny), that's when the 'unsupported operation attempted' error message was generated, then egui.exe became unresponsive, and a few seconds later dr watson (windows error reporting) intercepted, generating an application error (below).

so, there you have it...

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 2008-02-09
Time: 23:12:55
User: N/A
Computer: ********
Description:
Faulting application egui.exe, version 3.0.621.0, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00043151.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 65 67 75 ure egu
0018: 69 2e 65 78 65 20 33 2e i.exe 3.
0020: 30 2e 36 32 31 2e 30 20 0.621.0
0028: 69 6e 20 6e 74 64 6c 6c in ntdll
0030: 2e 64 6c 6c 20 35 2e 31 .dll 5.1
0038: 2e 32 36 30 30 2e 32 31 .2600.21
0040: 38 30 20 61 74 20 6f 66 80 at of
0048: 66 73 65 74 20 30 30 30 fset 000
0050: 34 33 31 35 31 0d 0a 43151..