Forums list
New topics
Topics list
Search
Help
Login
Register


Topic: «[Bug] AWM Beta 2 - Create New Window Rule , ActualWindowManagerCenter.exe Unspecified Error » on forum: Beta Testing   Views: 9480
 
Tristan Wolf
Registered user
 
Posts: 44
Joined: 02/21/2007
Posted: 02/26/2007 19:07:47
 
 
I received an error while trying to create a new window rule.

Problem Recreation

Reset All Window Rules
01) Make sure AWM is closed.
02) Go to the data directory of the Window Rules (defaulted to C:\Documents and Settings\[User Name]\Application Data\Actual Tools\Actual Window Manager)
03) Delete the file WindowRules.ini.
04) Open AWM.
05) Open AWM Configuration Manager.
06) You should see that all default Window rules are in place.

Delete All Specific Window Rules and Save
01) Open AWM.
02) Open AWM Configuration Manager.
03) Delete all specific window rules, starting with the Calculator entry through the Yahoo Messenger entry.
04) Click the "Saves Changes" button on the toolbar.

Attempt to Create a New Window Rule
01) Click the "Adds a new window rule to the current list" button on the toolbar.
02) You should get the error here.

Error Description

Quote
ActualWindowManagerCenter.exe
ActualWindowManagerCenter.exe has encountered a problem and needs to close.  We are sorry for the inconvenience.
If you were in the middle of something, the information you were working on might be lost.

If you click on the Close button, the Configuration Manager and AWM both appear to still be open.

If you click on the Debug button, you get the following error message:

Quote
ActualWindowManagerCenter.exe - Application Error
The instruction at "0x00447cc" referenced memory at "0x00000000". The memory could not be "read".

Click on OK to terminate the program.

Consequently, as I left this message box opened while writing this message, I also had SQL Server Service Manager crash and AVG AntiVirus 7.5 crash.  Very disturbing.

I will try to reboot and still see if I can recreate the error.

Thank you for your help.
 
Top
Tristan Wolf
Registered user
 
Posts: 44
Joined: 02/21/2007
Posted: 02/26/2007 23:56:57
 
 
Verified that the problem reoccurred after rebooting and following the steps I outlined in the original post.

Also, I looked in the Event Viewer and found the following:

Quote
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 2/27/2007
Time: 12:52:20 AM
User: N/A
Computer: [EDITED]
Description:
Faulting application actualwindowmanagercenter.exe, version 4.4.0.0, faulting module , version 0.0.0.0, fault address 0x00000000.

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 61 63 74   ure  act
0018: 75 61 6c 77 69 6e 64 6f   ualwindo
0020: 77 6d 61 6e 61 67 65 72   wmanager
0028: 63 65 6e 74 65 72 2e 65   center.e
0030: 78 65 20 34 2e 34 2e 30   xe 4.4.0
0038: 2e 30 20 69 6e 20 20 30   .0 in  0
0040: 2e 30 2e 30 2e 30 20 61   .0.0.0 a
0048: 74 20 6f 66 66 73 65 74   t offset
0050: 20 30 30 30 30 30 30 30    0000000
0058: 30 0d 0a                  0..    

Hope that helps a little more.  Thanks.
 
Top
Alexey Fadeyev
Administrator

Moderator
 
Posts: 1436
Joined: 09/30/2005
Posted: 02/27/2007 10:03:36
 
 
Wow, a truly professional bug report! Thanks, Tristan, the bug is confirmed and will be fixed in the release version.
 
Top
Tristan Wolf
Registered user
 
Posts: 44
Joined: 02/21/2007
Posted: 03/01/2007 08:57:38
 
 
Excellent!  Glad I could help.   :D  
 
Top


User(s) reading this topic
Number of guests: 1, registered members: 0, in total hidden: 0


Forums list
New topics
Topics list
Search
Help
Login
Register