Forums list
New topics
Topics list
Search
Help
Login
Register


Topic: «V5.2 configuration failure and shell crash under Vista 64 , Despite much testing, this only showed-up in 5.2 final. » on forum: Technical Support   Views: 10106
 
Jeffrey R. Broido
Registered user

Bona fide, old fart, retro hippie.
 
Posts: 44
Joined: 12/12/2007
Posted: 10/16/2008 08:08:20
 
 
Alex,

Well, despite much successful testing of 5.2RC1, and despite running well for days under 5.2RC1 and final with no issues, I had a pretty comprehensive failure this morning and it looks like it will require a reboot.

Here's the sequence:

1) Open the VNC P4.4.2 address book (the particular app. probably isn't significant).

2) Resize the app. window by dragging a corner.

3) Click the app. window's AIM wrench title bar button and click "Modify Applied Settings".

3) Click on the "Size" link and drag the target icon to the app. window.

4) AIM crashes.

5) OS presents "Close or Wait", close selected.

6) Restart AIM manually.  It starts, but, apparently, isn't successful reapplying its hooks, for AIM now appears not to be doing anything much (no title bar buttons, no extended options in context menus, etc.).  Note as well that whilst the configuration dialog opens properly, Actions/Stop and Actions/Unload do nothing, though it will shut down via tray icon right click/exit.  Restarting leaves it in the same state.

7) Right click tray icon/logging/enable logging.

8) At this point, my shell crashes, I select restart, but AIM still won't hook properly.

Logging is still turned on but there are no new entries in the log.  I haven't rebooted yet, for I expect you might want me to do something to capture my system's state.  If I don't hear from you within a few hours, however, I'll reboot and try the sequence again.

Regards and apologies for not catching this in the beta,
Jeff


______________________________________
NO STATEMENTS FLAGGED IN THIS ASSEMBLY
 
Top
Alexey Fadeyev
Administrator

Moderator
 
Posts: 1436
Joined: 09/30/2005
Posted: 10/16/2008 22:57:30
 
 
Wow, sad to hear this. :( Anyway, there are some details I'd like to clarify:

Quote
Jeffrey R. Broido wrote:

3) Click on the "Size" link and drag the target icon to the app. window.

Which "Size" link actually (Start/Fix min/Fix max/etc.) did you drag?

Quote
Jeffrey R. Broido wrote:
4) AIM crashes.

What actual application (Center.exe or Config.exe) crashed?

It looks like this situaion can't be recovered without full reboot so you can proceed with it. We'll investigate this issue further on our test machine. Thank you for the report and sorry for troubles.
 
Top
Jeffrey R. Broido
Registered user

Bona fide, old fart, retro hippie.
 
Posts: 44
Joined: 12/12/2007
Posted: 10/17/2008 08:38:07
 
 
Alex,

Sorry about that...  I should have mentioned that the size target icon I dragged was the top one, "Resize Window Automatically At startup to", with width and height both checked (315x509), the only option selected being "Keep aspect ratio".

I also should have pasted this:
__________________________________________

Product
Actual Window Manager

Problem
Stopped working

Date
10/16/2008 7:35 AM

Status
Report Sent

Problem signature
Problem Event Name: APPCRASH
Application Name: ActualWindowManagerCenter.exe
Application Version: 5.2.0.0
Application Timestamp: 2a425e19
Fault Module Name: StackHash_c5ce
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: 00000000
Exception Offset: 00000000
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional Information 1: c5ce
Additional Information 2: 4fc89cf20b38d46acbc7eca1c05a2e9a
Additional Information 3: 58bb
Additional Information 4: 618572261db48f1f57132e8311dab1f9

Extra information about the problem
Bucket ID: 849776027
__________________________________________

I did reboot after a couple of hours as I discovered that there were other coincident issues related to the shell crash which cascaded from the ...center.exe crash, such as my mouse driver losing button definitions.

Meanwhile, I just got up the nerve to try to recreate the problem and, just as before, the moment I hit "Apply", things started to happen and I was reminded that I'd forgot to mention that the first thing which happened (both times) is that windows which I'd minimized to the tray via AIM title bar buttons were all restored.  On the theory that if I didn't wait for the crash but told AIM to exit that it would remove its hooks properly, but it had no good effect and, in a matter of a minute, my whole system was frozen to the point that even the mouse pointer didn't move.

So, I'd say we have a recreatable problem; I'm just sorry I didn't discover it during testing (I did try resizing many other windows while testing RC1).

I'm leaving this text at the default size for your forum program either has only two sizes or I can't figure out how to specify it, for if I use the SIZE= key at all, I get huge text and if I don't, I get text almost too small for an old fart retro hippie to read!

Regards,
Jeff


______________________________________
NO STATEMENTS FLAGGED IN THIS ASSEMBLY
 
Top
Matt Rasmussen
Advanced user
 
Posts: 107
Joined: 05/25/2008
Posted: 10/17/2008 17:59:16
 
 
Hey guys,

I am running Vista 64 on one of my machines and I have tried to follow the steps above.  When I open a program that does not currently have 'specific settings' within the AWM program and I resize the window and then click the wrench icon, I don't have the option to select "Resize Window Automatically At startup to", I only have 'Resize Windows Automatically' and 'Resize Windows Manually' areas to select from.  Like this...(click image for full size)

User added an image
User added an image

Dragging any of those selection targets to the applications frame does not crash AWM or lock up my computer.

If I launch a program that IS currently defined with 'specific settings' in AWM and I follow the steps, I do get the selection mentioned in the steps, but when I enable that choice with the checkbox and drag the target to the application frame, nothing happens....

Hope that helps a bit, sounds like Jeff's problem is very specific to his machine and/or AWM configuration.
 
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