Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] File reload popup after Save + File size growing after resize and few saves #1655

Open
1 task done
glpnk opened this issue May 8, 2024 · 0 comments
Open
1 task done
Labels
bug Something isn't working

Comments

@glpnk
Copy link

glpnk commented May 8, 2024

Operating System

Linux

What's the issue you encountered?

  1. File was modified by external source message after saving in ImHex.
  2. If file size was increased, it's still increasing after next saves. (Not works with reducing file size and big reduce with small increase after)

How can the issue be reproduced?

  1. Create and Save OR Open small file (~2 bytes will be enough)
  2. Resize File (+n bytes)
  3. Save
  4. ImHex will ask for reloading the file, assuming that it has been modified by an external source. [BUG 1]
  5. Accept reloading, now your file looks bigger. But extra n bytes are not saved now, but looks like saved.
  6. Save + Reload few times. Your file is growing. [BUG 2]

ImHex Version

from commit 45a3bdffe on master (v1.33.1)

ImHex Build Type

  • Nightly or built from sources

Installation type

CLion build / GH Actions Arch Linux

Additional context?

Initially tested on Ubuntu 22.04 based distro running on BTRFS.

Windows seems not be affected by this issue.

I ask a friend with Arch running on BTRFS to test some latest build from GH Actions build artifacts. Issue was confirmed.

I don't know, is Apple affected or not.


Building small file commit was unsuccessful, so actually I use ca3708df71bc for testing.

In this version, the reload message appears a few seconds after the file is saved. But I think the issue is starts from small file commit.

If the file is larger than 128 MB, the issue does not occur anymore. (Because different access method is used.)


Not fixed by

#1654
WerWolv/libwolv#14

@glpnk glpnk added the bug Something isn't working label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant