I tried the new DiskMap plugin, on two different computers, on the root of their largest partitions (C: on one, D: on the other). On both systems, after calculating during some time, it hangs. It does not respond to Esc, nothing.
When I unload the plugin, or close Salamander, I get the error "DiskMap window close failed". After that, Salamander crashes. I just sent the crash report by e-mail.
I narrowed it down to a specific file. It is a *compressed* file of 65536 null bytes (attached for convenience).
Hope this helps!
Oh, and when it does work, I really like this new functionality!
DiskMap hangs and crashes Salamander
DiskMap hangs and crashes Salamander
- Attachments
-
- zerobytes.txt
- Save this file, NTFS compress it, and then try the DiskMap plugin
- (64 KiB) Downloaded 337 times
Groente, Michel.
-
- ALTAP Staff
- Posts: 5231
- Joined: 08 Dec 2005, 06:34
- Location: Novy Bor, Czech Republic
- Contact:
Re: DiskMap hangs and crashes Salamander
Could you please start two instances of AS, hang the first one and from the second choose Help > Task List command and break the hanged instance the Break button?
Bug report window should appear in the hanged instance. Please send use it's content.
Bug report window should appear in the hanged instance. Please send use it's content.
Re: DiskMap hangs and crashes Salamander
Yesterday, DiskMap freezed. I could only kill the complete Salamander prozess. For Bug report its to late.
Re: DiskMap hangs and crashes Salamander
Jan, please find attached the crash report.
- Attachments
-
- DiskMap hang.txt
- (25.54 KiB) Downloaded 319 times
Groente, Michel.
Re: DiskMap hangs and crashes Salamander
Thank you mdruiter for your great bug report! I was able to reproduce the problem and fix it
The interresting thing is Salamander and the DiskMap plugin report the the file occopies 0 bytes, but Windows (XP) Explorer reports size on disk to be 4kbytes. (When compressed the file becomes Sparse file and only contains information about the one zero-filled block)
Should DiskMap display size of the file according to Windows Explorer as 4 kbytes or according to Salamander as 0 bytes?
The interresting thing is Salamander and the DiskMap plugin report the the file occopies 0 bytes, but Windows (XP) Explorer reports size on disk to be 4kbytes. (When compressed the file becomes Sparse file and only contains information about the one zero-filled block)
Should DiskMap display size of the file according to Windows Explorer as 4 kbytes or according to Salamander as 0 bytes?
Re: DiskMap hangs and crashes Salamander
That depends on the real occupied disk space - the file could be actually stored somewhere in the MFT (Shred Files command warns about this after processing files smaller than 1024 B) or it could really occupy one cluster (~ 4096 B).zarevak wrote:Should DiskMap display size of the file according to Windows Explorer as 4 kbytes or according to Salamander as 0 bytes?
Ελληνικά rulez.
Re: DiskMap hangs and crashes Salamander
AFAIK all files smaller than 512 bytes are storred in MFT. Currently DiskMap doesn't handle this as I don't know any way of detecting files stored in MFT without reading the MFT directly. Reading the MFT requires admin (backup) privileges... (I'm not even sure if 512 bytes is The magic number or it depends on other things as well)
In this one case the whole file is storred in MFT...
In this one case the whole file is storred in MFT...
-
- ALTAP Staff
- Posts: 5231
- Joined: 08 Dec 2005, 06:34
- Location: Novy Bor, Czech Republic
- Contact:
Re: DiskMap hangs and crashes Salamander
It probably doesn't matter, be we prefer to report same size according to Salamander instead of Windows Explorer.zarevak wrote:Should DiskMap display size of the file according to Windows Explorer as 4 kbytes or according to Salamander as 0 bytes?