Page MenuHomeFeedback Tracker

ArmA 3 windows server is not releasing files after execVM, preprocessFile* and loadFile
New, WishlistPublic

Description

ArmA 3 windows server is not releasing files after execVM, preprocessFile* and loadFile. Please release the files.

Linux server is fine. No file locking behaviour.

Details

Legacy ID
3067976312
Severity
None
Resolution
Open
Reproducibility
Have Not Tried
Category
Scripting
Steps To Reproduce

_fileContents = preprocessFile "whatever.sqf";

After the contents are read, attempt to delete "whatever.sqf".

Event Timeline

cyckuan edited Steps To Reproduce. (Show Details)Nov 19 2014, 3:47 AM
cyckuan edited Additional Information. (Show Details)
cyckuan set Category to Scripting.
cyckuan set Reproducibility to Have Not Tried.
cyckuan set Severity to None.
cyckuan set Resolution to Open.
cyckuan set Legacy ID to 3067976312.May 7 2016, 7:51 PM
cyckuan added a subscriber: cyckuan.

Use-case for releasing files after reads or loads

  1. Accelerates script development, especially if the scripts are read from files.
  2. Allows hotfixes and run-time changes of configurations/settings.
  3. Increases interoperability and file-based interfacing.

Client-side, to release files held by a multiplayer session, it is necessary to back out to the multiplayer server selection screen.

Server-side, it is necessary to restart the server.

Please, prioritise this. Not releasing files after reads and loads is not very professional.

dedmen claimed this task.May 18 2020, 11:04 AM