Ticket #2581 (new defect)

Opened 8 years ago

Last modified 8 years ago

When an archive file grows to a certain size, some text files cannot be opened by MC

Reported by: toothandnail Owned by:
Priority: major Milestone: Future Releases
Component: mc-vfs Version: 4.8.0-pre1
Keywords: Cc:
Blocked By: Blocking:
Branch state: no branch Votes for changeset:

Description

When opening an archive using MC vfs (tested with both tar.gz and tar.bz2), once the archive size is over a certain size, some files within the archive cannot be opened or extracted. When the archive is tested it shows no errors, and the files can be extracted either by tar or by xarchiver.

If the archive is below 400 MB, the error does not occur, but, at some size above 400 MB, it starts to happen. The files that cannot be accessed can be small or large, and not all files are affected. I have not detected any pattern as to what files will be affected.

To reproduce, create a compressed tar (gzip or bzip2 both exhibit the problem) with mixed files, with a compressed size of 500 mb +. Open it with MC and open/extract files from the archive. Some of the files will not respond to F3, F4, F5 or F6 operations.

Recreate the archive excluding some files, reducing the compressed archive to less than 400 mb. Open the file with MC. Files that could not be accessed in the larger archive will now be able to be opened.

This occurs with 4.7.5 + (unable to test earlier versions). It also occurs with my own build of 4.0.0pre1.

If I can provide any further information, please let me know.

Change History

comment:1 Changed 8 years ago by andrew_b

  • Component changed from mc-core to mc-vfs

comment:2 follow-up: ↓ 3 Changed 8 years ago by andrew_b

How many free space in your temporary directory?

comment:3 in reply to: ↑ 2 Changed 8 years ago by toothandnail

Replying to andrew_b:

How many free space in your temporary directory?

Test archive - contents of /usr, .93 GB in size. With the archive open, 9.1 GB available for temp. Problem does not occur on all the files in /usr/doc/ but does for most.

Note: See TracTickets for help on using tickets.