P.S. This problem can be reproduced on all sites i am trying to get.
Do u mean that this happens only on my system? When u try to download a big site (more than one day), don`t u have a problem with OE taking up all the RAM, and being very heavy - freezing periodically for 5-30 secs, stacking, etc...?
> Can you try to minimize OE and then restore? Somehow Windows reallocates RAM after this trick and it shows less used RAM. Does this help?
Please let me know how it uses memory this way. I would also suggest to try
u r right the /noMap flag solved the problem, i forgot about it completly.
Why don`t u add it to the GUI?
also what is the difference between the two: NoMap and NoDB?
> Most possible that the memory is being occupied by the Project Map - a list of all downloaded files of the Project. To check this, can you run Offline Explorer Pro the following way:
> oe.exe /NoMap
> Please let me know how it uses memory this way. I would also suggest to try
> oe.exe /NoDB
> parameter independently.
> Thank you!
> u r right the /noMap flag solved the problem, i forgot about it completly.
> Why don`t u add it to the GUI?
Turning off a Map has its bad side - without a map you cannot remove a Project correctly, export it, backup, etc. Because OE would not know which files belong to the Project.
> also what is the difference between the two: NoMap and NoDB?
NoMap disables using a Map and adding new files there.
NoDB disallows using database which relates saved filenames and real online URLs. When a URL is too long (over 100 symbols), it is being truncated to 100 chars to make a filename and it is being added to the database (URL2s.* files). When OE parses a saved HTML page and finds truncated link, it can always get the original online URL if it needs to be redownloaded.