Cannot rename by QFile::rename

[jsulm]

@tham I don't think it's a bug. It sounds more like the file is still in use. Windows blocks renaming/deleting of used/opened files, but MacOS/Linux do not. You should check using https://technet.microsoft.com/en-us/sysinternals/filemon.aspx

[Eddy]

Also to add to @jsulm , I've had situations on windows, especially win8 and 10 where the user has windows explorer open in the same directory with the preview pane active. That might lock the file also.

[tham]

I find out the culprit, it is QImageReader.

static size_t num = 0;
QImageReader reader(name);
 reader.setDecideFormatFromContent(true);
 reader.canRead(); //after calling can read, the file will be locked
 bool const can_rename = QFile::rename(name, QString("img/sos%1").arg(num++));
qDebug()<<"can rename:"<<can_rename;

Is this an expected behavior?

In case it is a bug, I create a small project to reproduce the issues

I create a minimal project to reproduce the situation, place at mega.

Things to noticed :

1 : copy img_links.txt to your shadow build folder

shadow_build
--debug
--release
--img_links.txt

2 : Create a folder "img" in shadow build folder

shadow_build
--debug
--release
--img

[tham]

@jsulm said in Cannot rename by QFile::rename:

I don't think it's a bug. It sounds more like the file is still in use. Windows blocks renaming/deleting of used/opened files, but MacOS/Linux do not.

Thanks, learn new things. Looks like QImageReader blocking the file.

[jsulm]

@tham That could be actually a bug in QImageReader.
canRead() should just check whether the image can be read and close it if it was opened to check.

[SGaist]

The internals are a bit more complex than that.

I'd move the QImageReader code in its own scope so it gets destroyed when not needed anymore and then you can go on move your files around.

[tham]

@SGaist said in Cannot rename by QFile::rename:

I'd move the QImageReader code in its own scope so it gets destroyed when not needed anymore and then you can go on move your files around.

Thanks for the suggestion, I do that already and now it works :)

No matter it is a bug or not, I think this api is counter intuitive, if QImageReader would lock the file, it should have a close api or mentioned in the document.

However, I open a bug report at jira.

[Mishko]

I had a something like this problem with file raname after move application from Linux to windows, But I rename file with names which are taked from text file separated by new line. At Linux if have list of names readed from file we must remove only last one symbol ("\n") from string (you cant set file name if at newNamr is cariage move symbol). At windows you must remove TWO symbols from the end of string (new line defined by "\r\n"). May be it will help someone

[efofex]

@SGaist I have just had exactly the same issue with QImageWriter. It keeps the file open/locked on Windows after writing. Moving it to it's own scope fixed the issue. I think that the documentation for QImageWriter needs to be updated to indicate this behaviour.

[SGaist]

@efofex Patch submitted.