Frank wrote
Those seriously affected perhaps could turn on logging in Action > Preferences and provide CoffeeCup with a copy of the log file covering the time the problem occurs.

Done that as default for a long time ago
sent it along with the video showing the freezing as it happened (caught it 3 times now on video) sometimes the file is so long I get tired of scrolling down, and it's full choc a bloc of errors, but so far again it would seem that the CC Gurus unable to find and solve the issue.


Frank Wrote
In the above circumstances, I wonder whether it relates to some specific settings in the program, such as Auto Backup

I have done many combinations of "Auto Back-Up Too" and it never seems to be that, Infact now I have it set to every 2 minutes so that when it crashes or becomes non-responsive, I don/t lose too much work.

I also sometimes abandon a project and start again from scratch, thinking maybe its a corrupt file,, just for it to happen again at some point

Just an Observation
The Project File is either freezing or white-out, I have just noticed it gets worse and more frequent when I have
a Reveal component(s) on a page, I am on with a project now, it has 4 pages at the moment, 1 of which has a total of 13 modals (reveal) acting as a slideshow gallery, over the course of this day, as I added more and more SD slowed down to a standstill and has crashed 4 times.
Restarting Sd is OK for 3 minutes or so until it comes to needing one of the reveals content editing, at which point it almost stops once again. This is only info for anyone interested or following this thread or experiencing similar, it would be interesting to know if you have a reveal (modal) on the page.

When it sticks or becomes unresponsive I have discovered that at that time it was using around 300mb of memory, I have no idea if that's normal or excessive or if that's somehow the culprit, perhaps a Guru will know

300MB of RAM usage by SD seems trivial compared with the usage by many other programs.

I think that Wayan may well be onto something with the matter of frameworks and particular parts of frameworks. Perhaps there are certain things one can do in SD that cause certain antivirus programs (wrongly) to slow things or stop them - not necessarily immediately.

When in a situation such as Wayan describes one could perhaps test this as follows -
1. turn off the connection to the Internet so as to remain safe from attack;
2. turn off the antivirus/security program(s) and see whether SD now performs without the problem;
3. turn the antivirus/security program(s) back on and restore the Internet connection.

It may well be that doing the above will simply prove that the problem isn't antivirus related. Eliminating various possible causes may, however, help the CoffeeCup team find the actual cause(s).

Frank

UPDATE

First sorry John if it seems I have hijacked your thread but there is a relevance.

Today, here is what I have done and discovered

1/ As per Frank's suggestion,
I totally disabled my anti-virus/firewall etc disconnected the rubbish WIFI we have here
I then opened the project file which kept slowing down/stalling and was unresponsive.
after only 10 minutes it started again, just like before

2/ I then opened a brand new project file (leaving the first one open)
I then started to replicate the original project file,
5 pages and 4 hours later the new project file was still working pretty good, by the way, I did NOT put any REVEAL MODALS like in the 2 pages in the original project file.

3/ I then opened the original project file (which had been sitting there), and it was still almost totally unusable, although it didn't crash or stick.
after 10 minutes of attempting to edit text/images etc I gave up.
4/ I returned to the second (new) project file and added 1 reveal Modal element, things were still functioning, so I added another, and Loh and behold it started lagging, by this time Site Designer had been in use for at least 6 hours continuous (which for me is like only 1/2 days work when building sites for people.)
I added a further 13 reveal modal components (duplicated the one already there)
suddenly there it was....... it slowed down to almost a standstill.

I then closed both project files and opened Site Designer, this time with the BOOTSTRAP 4 framework, and proceeded to replicate the site,

here we are another 4 hours down the line 5 pages done, NO REVEAL MODAL things because I need to build them separately (not available as a component in bootstrap) the thing is though the project is totally and utterly a joy to work with (except of course it's bootstrap, not my favourite framework) no lagging no delays sweet as a nut.

CONCLUSION
It would therefore appear to me that the foundation framework, has something buggy going on somewhere, It can't be the ANTI VIRUS or Firewall stuff, because it still does it, even when they are disabled
There must also be something to do with the Reveal Modal component from Foundation because the two Foundation framework projects got worse as I added the Reveals.

Tomorrow
I shall make a video or two demonstrating the issues (too tired now)

Food for thought though, I know it's not strictly scientific but it maybe a starter for 10.

Very interesting reading about your experiment, Wayan. I have used the reveal method for some projects and never had problems, but this was some time ago (as in some SD builds ago). About 2-3 years ago I built a gallery for someone with 30-something images, all with the reveal and no issues. So my question: when did the troubles you are describing start? Do you remember from which SD build onwards it started to deteriorate?

I have used Foundation quite a bit, and I have noticed that some of the built-in components have had to be rebuilt after some time. Orbit is one of them. I don't know, but my hunch is that the components stay the same in build after build, and some might be way past their sell-by date. Maybe it is time to take a closer look at the reveal component?

Hi Inger
not sure about how long, or how many builds ago, but I would say that since the last 3 or 4 it has got worse

the one thing I have noticed today is that when I had the anti-virus and firewall disabled the first project still slowed down a lot, but it didn't stick or crash, which did happen quite often before.

I'm going to do another in Materialize tomorrow, just to see

Todays Update (5-July-2022)
Firewall & Anti-Virus enabled
Site Designer now open for 6 hours with continuous working

Project 1
The Foundation Framework original project - unworkable without saving closing and re-opening unresponsive after a while, especially within the Reveal Modal and editing text

Project 2
The duplicated (project 1) Foundation Framework Project is a little bit better than the original project, in so much as it doesn't need saving & restarting so often, but it is getting slower as time goes by

Project 3
The duplicated project in the Bootstrap framework. I never thought I would hear myself saying this but
..........................OH JOY what a difference a framework makes
still working as sweet as my mom's lemon meringue pie
I am on with adding the first (bootstrap) modal, a bit of a learning curve for me, but so far GRRRrrrrreat
So I stand by my previous comments, that there MUST be a bug in the Foundation Framework, which gets amplified when a Reveal Modal (or 2) is added to a page, what that bug is, how to find it and fix it I wouldn't know

1/2 day off for me today so will continue tomorrow (Indonesian Time)

W

Today's Update (13-07-2022) for those following or interested in the developments

Project 3 Using "Bootstrap" (project now open for 8 hours: 6 hours of continuous use).

Everything continued pretty much as before, I added a Bootstrap Modal Component from Inger's components page, her component comes with 8 thumbnails & bootstrap modal reveal windows, It needed quite a bit of customised styling to make it work & function as the client wanted it. I also increased the number of Reveal modal components to on the page to 18 (14 in a gallery style (as per Ingers Component and 4 separate on the page)

After about the first 3 hours of continuous use, things started to slow down a little bit, but not as much as in the foundation framework projects.

I then created a new page exactly the same as the one with the reveal gallery(same Images) and the 4 separate reveals (this one for the Indonesian version (language (images etc same), )

A further 6 pages with just the 4 separate reveal modals.

Sad to say, that now the project file is acting exactly the same as the Foundation ones and is freezing, slowing down to almost a full stop, on closing and re-opening after a coffee break, it works well for about 30 mins before acting up.

Conclusion
I now have no ideas or theories.

Next step
Project 4
Using "Frameworkless" (mobile first)

Hi Wayan, try the 'Easy modal gallery' that I have in my component shop. Choose your framework, there is a version for all of them - even for the HTML Editor. This is something Frank and I have put together. Frank made the magic with the js.

I have made the real project file outside of site designer using good old Dreamweaver, no laggig no crashing the client couldn't wait.
I have started one in frameworkless just to see but I suspect that there is something amis between my pc and site designer, may e it's too much to expect it to go the distance when it's been open for a good few hours, but then that's my normal working day 7 days a week (occasional 1/2 day). Dreamweaver/Photoshop and others seem to be able to cope with that workload.