USA
Joined: Oct 7, 2015
Post Count: 199
Status:
Offline
Re: Suddenly, huge file size...
A copy/paste operation between files could be a possible track,
I think this might be what is creating the folder with the sub-folders and files. I looked through mine and it looks like it is filled with models I've copied/pasted within the plan, although I didn't look through every folder.
---------------------------------------- Hawk
USA
Joined: Mar 25, 2015
Post Count: 153
Status:
Offline
Re: Suddenly, huge file size...
OK, it's not solely linked to copy/paste between files.
The past few days, I've been compressing and checking each save, being careful not to copy/paste from file to file -- and until a few moments ago, it looked as if that might be the answer. Unfortunately, I just saved a plan that should have weighed in around 190 Mb uncompressed, and it ended up over twice that size. Compressing and opening the zipped file shows it contains a recursively saved plan.
The only oddity I noticed was that during the save process the UI seemingly "jumped" -- shifted over a few pixels , with the scroll bar on the object pane disappearing. Whether that's of any help, I don't know....
I have a suspicion or two to investigate, but wanted to pass along the little I've learned.
USA
Joined: Mar 25, 2015
Post Count: 153
Status:
Offline
Re: Suddenly, huge file size...
I'd worked for most of a day with no problems, with the plan working its way to about 200 Mb. (I added several complex models built in Sketchup, so the sudden 50 - 60 Mb jump is normal.) However, after making a few tweaks to fix corrections I'd subsequently lost when reverting to an earlier save, I hit 'save' one last time -- and ended up with a 400 Mb file. (Fortunately, I actually hit 'save as,' so I only lost my final half-hour of fiddling about.)
Once again, I *didn't* copy/paste from file to file; however, I *did* perform a number of copy/paste operations from level to level.
I also deleted several [empty] levels I'd mistakenly added by hitting the '+' tab instead of my target.
In addition, I copy/pasted several *walls* -- not just furniture -- from one level to another. (For each of the 6 floors in my plan, I'm using as many as 7 co-located levels, for a current total of 24? 25? levels.)
I also experienced a previously unseen glitch earlier, when, after modifying an object's materials, its normal onscreen display was replaced by a featureless box with a texture applied. (As the texture happened to be the JPEG used as a diffusion map for the standard mirror object, after I'd edited a handful of objects, my plan looked like a mid-1990s showcase kitchen: shiny stainless steel as far as one could see.) Objects rendered without a hitch; only their 2D representations were corrupted.
I don't know if this suggests the recursive bug had occurred before my actual attempt to save, but while the program was laboriously writing its 400 Mb plan to disk, I took a look at sh3d's working directories. Inside the contemporary 'work' folder, I discovered two [auto?] saved plans, *each* weighing in at 400+ Mb. (Unfortunately, I failed to make a note of their respective timestamps, but IIRC, at the time of the save, they were both a dozen or more minutes old.) During the actual save, it appeared that both my .sh3d data file and the .RECOVERY file were being incrementally saved in tandem. Once the save was complete and I exited the program, both the .RECOVERY file and the current work folder were deleted automatically. (However, I still have four work folders dating from the 24th and 27th, totaling 1.1 Gb. I assume these are the result of a program crash -- quite possibly during my unsuccessful attempts to load a .sh3d file from which I'd removed a recursively saved plan -- and can safely be deleted.)
Unsurprisingly, every suspicion I had (primarily involving multitasking during the save process) has proven unfounded, and the problem occurs *just* infrequently enough that when it does, I typically can't reconstruct exactly what it was I'd done since the last problem-free save. When I return to sh3d later tonight or tomorrow, though, I'm planning to log each action, in hopes of nailing this sucker.
USA
Joined: Oct 7, 2015
Post Count: 199
Status:
Offline
Re: Suddenly, huge file size...
This is of no help to this particular issue but I thought I'd mention that all folders and files in the work folder can be deleted if they start getting to be too big, with no negative issues, as per Puybaret stating so in this post:
France
Joined: Nov 7, 2005
Post Count: 9433
Status:
Offline
Re: Suddenly, huge file size...
[...] all folders and files in the work folder can be deleted
Yes, but be sure to quit Sweet Home 3D first.
HawkDawg, thanks for proposing a file that shows this issue. I've got already one but yours might reveal something else...
mazoola, thanks for your patience to search a way to reproduce this issue. I don't think that saving the .recovery and .sh3d files at the same time is a problem, because the tasks that handle these operations work on copies of the edited home, so they don't share any data.
----------------------------------------
Emmanuel Puybaret, Sweet Home 3D creator
USA
Joined: Mar 25, 2015
Post Count: 153
Status:
Offline
Re: Suddenly, huge file size...
mazoola, thanks for your patience to search a way to reproduce this issue. I don't think that saving the .recovery and .sh3d files at the same time is a problem, because the tasks that handle these operations work on copies of the edited home, so they don't share any data.
Sorry; I should've made it clear I wasn't reporting this because i thought there was a potential link, but simply in case what I was seeing wasn't what you expected. It's been 15? 16? years since I last did any serious Java development -- and, frankly, the only serious thing about it was that I charged someone for doing it; it was embarrassingly simple work -- but in subsequent years and using subsequent languages, I've occasionally run into problems when the language didn't execute concurrent processes the way I expected or did so in differing orders under differing conditions. Since I managed to catch the save processes in the act this time, I figured I'd pass it along.
I realize this is likely to be extremely difficult to reproduce, and likely even harder to correct -- I seem currently to be experiencing it more frequently than most, and even I can't get it to misbehave on demand. (I slapped sh3d around all evening without ever getting it to fail -- and that was after importing by far the ugliest furniture item to date: 50k+ faces, 230+ materials.) Right now I think I have procedural work-arounds in place -- namely, frequent and liberal saves -- so I'm no longer all that inconvenienced by it. I'm going to keep trying to see if I can reproduce the problem consistently, and as I try things I'll continue to post what will likely be completely irrelevant updates and documentation from time to time, just on the off chance something helps you troubleshoot this problem. If (when ) what I post is pointless, feel free to ignore it!
USA
Joined: Mar 25, 2015
Post Count: 153
Status:
Offline
Re: Suddenly, huge file size...
So, after more than a month without this problem repeating,* I just now went to save a model that's been weighing in around 255 Mb -- and ended up with a 507 Mb model. Since the previous save, I'd performed no cuts-and-pastes between files or levels; instead, all I did was tweak a half-dozen or so light sources, duplicate another half-dozen or so, resize a couple of doors, and make an object invisible.
Emmanuel, could the problem be as simple as requesting a save while (or right as) the application is auto-saving the model? As best I recall, before I went to click 'save,' I heard my drive laboring as if under an automatic save. That's about the only pertinent potential linkage I noticed.
Maz __________
* Admittedly, I've not worked with SH3D daily during that period; 1 day out of 3 is probably a good estimate.
France
Joined: Nov 7, 2005
Post Count: 9433
Status:
Offline
Re: Suddenly, huge file size...
Thanks for keeping posting your reports about this issue. I'm sure all your comments will finish to give me the idea that will help to fix this bug. Autosave and save tasks work on copies of a home and on different files, so even if they run at the same moment, I don't think this should cause any problem.
----------------------------------------
Emmanuel Puybaret, Sweet Home 3D creator
) what I post is pointless, feel free to ignore it!
