WhatIsHang 1.27
|
Date Added: |
Feb 18, 2015 03:08 AM |
Publisher's Description: |
Sometimes, Windows or a running application hangs, the user interface abruptly stops responding, and you cannot determine what has caused the problem or how to troubleshoot the issue. This utility tries to detect the software or process that is currently hung, and displays some information that may allow you to sort out and understand what exactly is at the root of such unexpected behavior. Most of the information displayed in WhatIsHang's report, like Call Stack, Stack Data, Processor Registers, and Memory Data is designed for users with Windows programming knowledge. However, WhatIsHang also presents a list of strings and dll files related to the hang issue that can help users without programming skills understand and overcome the causes of the problem and restore normal operation.
System Requirements And Limitations
This utility works on any version of Windows, starting from Windows 2000 and up to Windows 8. Both 32-bit and 64-bit systems are supported.
In order to detect hang problems of 32-bit applications, you must use the 32-bit version of WhatIsHang, even if your operating system is 64-bit.
In order to detect hang problems of 64-bit applications, you must use the 64-bit version of WhatIsHang.
On Windows 7/8/2008/Vista with UAC turned on: WhatIsHang cannot detect hanging application if it's running with SYSTEM or Administrator privilege. In order to solve this problem, you have to right-click on WhatIsHang.exe and choose 'Run As Administrator'.
Some hang problems cannot be detected properly by WhatIsHang, for example:
Programs without any user interface.
When the program hangs because one thread waits for the other one. (In this case, WhatIsHang will show the details of the waiting thread, but the problem might be in the other thread)
But... Starting from version 1.05, you can use the experimental 'All Threads' report to display the information about all running threads.
When the entire system hangs - In this case WhatIsHang won't be able to run...
Versions History
Version 1.27
Fixed bug: The 'Automatically Get Report' menu item failed to work properly.
Version 1.26
Fixed bug: WhatIsHang failed to remember the last size/position of the main window if it was not located in the primary monitor.
Added 'Run As Administrator' option (Ctrl+F11), which allows you to easily run WhatIsHang as administrator on Windows Vista/7/8/2008.
Version 1.25
Added 'Automatically Get Report' option. When it's turned on, WhatIsHang automatically generates a report for a freezeing program around 2 seconds after it's detected, without selecting it and pressing F9.
Added 'Always On Top' option.
Version 1.20
Added x64 build, for getting a report about freezing 64-bit applications.
Added list of all loaded modules to the report.
Fixed the flickering problem in the status bar.
When WhatIsHang fails to extract information from the process, it now displays a message about that in the report, instead of showing report full of zero numbers...
Version 1.15
Added 'Start As Hidden' option. When this option and 'Put Icon On Tray' option are turned on, the main window of WhatIsHang will be invisible on start.
Version 1.10
Added 'Put Icon On Tray' option.
Version 1.07
When a program hangs because it waits to another system object (WaitForSingleObject API Call), WhatIsHang now displays the type of the system object and its handle, on the Remarks section.
Version 1.06
Fixed the all threads list to display the correct start address.
Added the Thread ID into the report.
Fixed bug: Ordinal function names were not displayed properly.
Version 1.05
Added 'All Threads' experimental report (Ctrl+F9), which displays a report about all running threads, as opposed to the standard reports that displays a report only for the thread that stopped responding. Be aware that 'All Threads' report might be quite large.
|
Screenshot: |
|
Documentation: |
http://www.nirsoft.net/utils/what_is_hang.html |
Last Download: |
Mar 29, 2024 11:16 PM
|
Downloads: |
225 |
OS: |
Windows |
Rating: |
|
|
|
