[MC-12074] Textures can't be overwritten while in-game Created: 16/Mar/13 Updated: 27/Apr/14 Resolved: 11/Aug/13 |
|
| Status: | Resolved |
| Project: | Minecraft: Java Edition |
| Component/s: | None |
| Affects Version/s: | Minecraft 1.5, Snapshot 13w11a, Minecraft 1.5.1, Minecraft 13w37b, Minecraft 13w41b |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Robin Fernqvist | Assignee: | Unassigned |
| Resolution: | Invalid | Votes: | 3 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| CHK: | |||||||||
| Confirmation Status: | Community Consensus | ||||||||
| Description |
|
Hello! Sometimes i can save the image and then tab to minecraft, hold F3 and press T and the texture is updated, but most of the times i get an error prompt saying the "file is already in use". But if i wait for like 2-5 minutes i can save it again (without closing minecraft).. The only way to solve this right now is to close minecraft, save image, re-open minecraft and log back in, or wait 2-5 minutes. |
| Comments |
| Comment by Tails [ 11/Aug/13 ] |
|
Texture packs are obsolete, if you have issues with resource packs, please let us know |
| Comment by Tails [ 21/May/13 ] |
|
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. |
| Comment by Ben W [ 14/Apr/13 ] |
|
Happened to me in 1.5.1. Just started playing around with making a texture pack, and ran into this same issue. It's not a major project of mine, so this is only a minor bug for me, but yeah. Notably, I found that this is still an issue even when the texture pack I'm trying to modify is not the active one. This is obviously a bug, as Minecraft shouldn't be reading from any pack other than the active one, right...? As mrheat and C.J. Wijtmans said, the cause is obvious: Minecraft is forgetting to release a lock on the texture pack zip file, and as a result retains exclusive access to the file when it's not strictly needed. |
| Comment by C.J. Wijtmans [ 17/Mar/13 ] |
|
i Guess it would be an easy fix then. file.close() |
| Comment by user-571ee (Inactive) [ 17/Mar/13 ] |
|
I guess the files aren't properly closed in the Java code. Obviously they are closed by the Java garbage collector. This is why it works after a few minutes. So yes, this is a bug. |
| Comment by Robin Fernqvist [ 16/Mar/13 ] |
|
Well yes, that's how they work currently, and if they're not intended to work this way, it's a bug. |