I updated Sweet Home 3D 2.5 to Beta 4 to avoid problems with temporary working files that were wrongly deleted (this happens rarely).
Now, these files are stored in the work directory of your personal application directory (eTeks\Sweet Home 3D\work under Windows, eTeks/Sweet Home 3D/work under Mac OS X and .eteks/sweethome3d/work under Linux).
Please can you confirm it works correctly on your system and that temporary files are deleted once you exited the program?

Sweet home 3d 3.3
Windows 7 Home Premium 64 bit

I noticed a sudden decrease of free space on my limited SSD, over 2-3 days. After cleaning up lots usual stuff like temp directories, recycle bin, etc I stumbled across 1.5 GB of space being used by eTeks\Sweet Home 3D\work. Not knowing what is this folder supposed to contain I immediately googled and arrived at this thread.

Since you were at that time asking if the "work" directory is being cleaned up after app exit, I thought I would explain this incident. I am actually new to this software, been using it since a week or so. I have installed many model packs available from sourceforge and a couple (may be 5-6) models from Google 3d warehouse. Also I have installed 9 plugins. That was about the software data.

Talking about the usage. I have till now created around 9 files. Been extensively closing and opening the files. A couple of renders using the advanced photos plugin and the inbuilt renderer.

Currently I see 26 Folders 155 files under "work" folder. Each folder is around 30 MB and starts with "3300-"
I haven't yet deleted these stuff which I assume can be safely deleted. So if you might have some time to work on this, or think the data in this folder could give some clue to the issue I would gladly help.

PS:
I just checked the folder with oldest modified date in the "work" folder. Is there a way to verify the time when I installed the software. So if it has been happening since freshly installed, we can rule out all plugins and other usage as the culprit.

Thanks.

[Note from moderator: moved the message in a separate thread]