© J.C. Kessels 2009
MyDefrag Forum
May 19, 2013, 08:21:34 am
Welcome,
Guest
. Please
login
or
register
.
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
News
:
Home
Help
Search
Login
Register
MyDefrag Forum
>
MyDefrag v4 Forum
>
Bugs and problems
>
mydefrag 4.12 crash w/ debuglog
Pages: [
1
]
« previous
next »
Print
Author
Topic: mydefrag 4.12 crash w/ debuglog (Read 1061 times)
b0b0b0b
Newbie
Posts: 2
mydefrag 4.12 crash w/ debuglog
«
on:
August 05, 2009, 01:04:03 pm »
159gig drive, dual xeon ht 2.8ghz, win 2k3, mydefrag run through remote desktop connection 256 colors 1920x1200 resolution. remote desktop client may have been minimized at time of crash, not sure.
# See the 'MyDefrag.log' file for information intended for endusers. This is the debug
# logfile. The contents is highly technical and not documented. See the 'Debug' setting
# or the '-d' commandline option to control the level of information in this file.
#
Version: MyDefrag v4.1.2
Date: 2009/08/04 22:41:29
Windows version: v5.2 build 3790 S
Commandline: "C:\Program Files\MyDefrag v4.1.2\MyDefrag.exe" -r SlowOptimize.MyD
Working Directory: C:\Program Files\MyDefrag v4.1.2
InstallPath = C:\Program Files\MyDefrag v4.1.2\
22:41:29 Analyzing the commandline.
22:41:29 Commandline argument '-r' accepted, added 'SlowOptimize.MyD' to the scripts.
22:41:29 Running script: Language.MyD
22:41:29 Running script: SlowOptimize.MyD
22:41:29 Running script: Settings.MyD
22:41:29 Processing disk C:
22:42:40 Loading list of unmovable files
22:42:57 Reclaiming the NTFS reserved area
22:42:57 Zone 1 of 5
22:42:58 SortBy
22:43:00 Vacating free area
22:43:01 Zone 2 of 5
22:43:05 SortBy
22:43:56 SortBy
22:45:23 Vacating free area
22:46:24 Could not get a write lock for 'OpenItemHandle'! Forcing a crash for debugging purposes...
I have crashed!
Command line: "C:\Program Files\MyDefrag v4.1.2\MyDefrag.exe" -r SlowOptimize.MyD
Current context locks:
DrawDiskMap
DrawClusters
Exception: ACCESS_VIOLATION (the memory could not be read or written)
1. At line (unknown) in (unknown)
Logged
jeroen
Administrator
JkDefrag Hero
Posts: 7155
Re: mydefrag 4.12 crash w/ debuglog
«
Reply #1 on:
August 05, 2009, 04:09:14 pm »
Your logfile shows that MyDefrag had trouble updating the display, there is a 60 seconds timeout. Perhaps this was caused by the remote desktop, in my experience remote desktop software can use a lot of CPU and make the display very slow. So MyDefrag generated a crash for debugging purposes. In the next version I will be lengthening the timout to 15 minutes, and change the message in the logfile.
Logged
Pages: [
1
]
Print
« previous
next »
Jump to:
Please select a destination:
-----------------------------
MyDefrag v4 Forum
-----------------------------
=> Announcements
=> Questions and help
=> Bugs and problems
=> Requests for new features
=> Scripts, and other contributions
-----------------------------
JkDefrag v3 Forum
-----------------------------
=> Announcements
=> Questions and help
=> Bugs and problems
=> Requests for new features
=> Programming with the library
Loading...