Publisher, RAM?

[candela.francisco]

Good afternoon, I have an imac with 8GB of RAM.
Publisher consumes all RAM and stops responding.
there's a solution?

[GarryP]

Welcome to the forums.
I have Publisher running on Windows 10 and it’s not taking much more than 530MB. I don’t think it will take much more memory, by itself, on a Mac.
However, that’s just an ‘empty’ Publisher with no document and therefore no images or anything else which will take up memory.
How much memory does Publisher take on your system when you have no open document?
Would you be able to supply a screen grab of your system resources while Publisher is running with no open document?

[Palatino]

Publisher together with Safari is a very bad combination.

(Mac mini late 2014)

[R C-R]

28 minutes ago, Palatino said:

Publisher together with Safari is a very bad combination.

(Mac mini late 2014)

FWIW, I often run Safari & APub on my old iMac (specs below in my sig). Although with only 8 GB of memory, as you might expect APub does slow down considerably as the document size & complexity increases, it makes very little difference if Safari is also running at the same time.

[Palatino]

The working speed makes no noticeable difference. Safari with some tabs, however, leads to increased crashes of the OS. I think the too small memory is the cause.

[R C-R]

2 minutes ago, Palatino said:

Safari with some tabs, however, leads to increased crashes of the OS.

Do you really mean the OS itself crashes (e.g. a kernel panic or a totally non-responsive lockup with a frozen pointer)?

I have never seen any app or combination of apps do that, other than when there has been an underlying hardware issue, or when there is so little free space on the startup drive that the memory manager can't page enough data out of RAM to have enough left to run some essential system level service.

[Palatino]

12 minutes ago, R C-R said:

… or a totally non-responsive lockup with a frozen pointer)?

There. But in the end, it makes no difference.

[R C-R]

19 minutes ago, Palatino said:

There. But in the end, it makes no difference.

If by "there" you mean a total lockup with frozen pointer, I have only seen that when there is a problem with a peripheral or its driver, with bad RAM, or when there is some other factor involved that relates only indirectly to the apps that are running, Affinity or otherwise.