Instability on Mojave?

[blw]

This is almost not fair, but it's happened... For reasons unrelated to Publisher, I had to upgrade to Mojave this week. (I was getting a panic in a GPU driver, and this bug was corrected in Mojave.) Since the upgrade, I've had a fair number of suspicious things happen in Publisher:

• Twice when I've asked to save, Publisher got stuck in a loop, eating 2+ CPUs for minutes at a time. One of those times, it stopped eating CPU and went into "not responding" state. That took a Force Quit to resolve. In that case, when I restarted, the crash file was noted and the recovery was good. I lost a minute or two's worth of work, but basically nothing. The second time just happened, and this time the CPU kept going. I did a quit on it, and it asked to save open files. I said yes. It then refused to quit, so I had to Force Quit it. Upon restart, the recovery file went back to a point in time many minutes ago - probably 20 or 30. Curiously, when I saved the recovery as a junk file and then loaded the saved version, it was correct. Bear in mind that these occur when I save, so it's not entirely obvious which save operation accomplished the deed.
• At least twice and I think three times, when I went to edit text in a text frame, I was simply unable to select anything in the frame! It was if the code thought that I was in some other mode. I'm pretty sure that I selected some other object (probably a picture within a picture frame, almost certainly not another text frame) and then returned to the offending text frame, whereupon sanity was restored.
• I have never tried hyphenation whilst running on High Sierra, but when I selected US hyphenation, I seem to get no hyphenation. This could easily be cockpit error, but if so, there is still no feedback to inform the offending user.
• I think I know how text styles are supposed to work, but I couldn't get them to propagate in this document. I went to a text frame, selected some text, and then modified the Body style. The modification stuck, and the "result" window confirmed this. However, when I applied this now-updated style in other text frames, the updates did not seem to apply.

I'm running beta version 140 after updating to 139 and having it auto-update to 140. Obviously I'm on Mojave, and I think it's the only version of same.

[jmwellborn]

I am on Sierra but am having the same problem every so often with trying to get the text tool to appear in a text frame.  Especially maddening is to create a new document, place a text frame across an entire page, then set the empty text frame to a 2-column format, and then select the text tool, click inside the first column and — nothing.  Back and forth between the text tool and the move tool.  Still nothing.    If I create a single text frame, click inside it, and create some text and THEN change the format to 2 columns, I can continue to type.   Going barmy.

[blw]

Maybe it's the two-column thing? Mine are two columns also. Fortunately it doesn't do this all that often, seemingly about once every third hour or so.

[Chris_K]

HI Blw

Are you saving these files an any particular location is it on you machine or is it on a cloud drive or network drive, USB stick etc?

I'm getting hyphenation in US here. They hyphenation isnt as strong as it probably should be but this is being tweaked all the time so it may improve.

I;m not getting any issue selecting and typing in text frame with columns or with applying text styles. Are you able to provide any screenshots or video to demonstrate your issue?

Cheers

[blw]

My files are stored on a local SSD, in fact on the internal, built-in SSD of the system. I suppose it's worth mentioning that the file in question is 1.7GB in size - there are many images.

Selecting in text frame, or failure to do so: no, I have no evidence. It's happened several times, but as noted above the way to "fix" it is to click somewhere else, then come back to the text frame. I have a strong suspicion that if I  knew how to do a video "screenshot," the very act of clicking something else (QuickTime?) to start recording it would likely chase the bug away - a Heisenbug if there ever was one.  Note that jmwellborn above has apparently encountered the same problem.

On the hyphenation, I think that I've messed up the text styles in this document. I created a completely new document and the hyphenation works. However, in this document, I think the problem is that my edited text styles don't seem to be taking globally.