Hangs when editing or creating hyperlinks

[Motljus]

After updating Affinity Publisher 2 to version 2.3.0 I am getting crashes every time I try to access the hyperlinks popup. Either by trying to edit an existing hyperlink or creating a new hyperlink.

The program hangs in Windows 10 and becomes completely unresponsive. The rest of Windows works fine, and nothing lags, but the program is totally unresponsive from mouse clicks from that point on. The only way to continue is to kill the process in the task manager.

Is there a way to create an additional error report for what is happening and what is causing the crash?

I checked the regular Log.txt and it only shows the things I did prior to the lockup.
 

[2024-01-02T15:08:38.972+0100] Affinity Publisher 2
[2024-01-02T15:08:38.973+0100] IsSandboxed: Yes
[2024-01-02T15:08:38.973+0100] AppDataPathForCurrentUser: C:\Users\Daniel\.affinity\Publisher\2.0
[2024-01-02T15:08:38.973+0100] AppDataPathForCurrentUserPersisted: C:\Users\Daniel\.affinity\Publisher\2.0
[2024-01-02T15:08:38.973+0100] AppDataPathForAllUsers: C:\ProgramData\Affinity\Publisher\2.0
[2024-01-02T15:08:38.973+0100] CommonDataPathForCurrentUser: C:\Users\Daniel\AppData\Local\Publishers\3cqzy0nppv2rt\Affinity\Common\2.0
[2024-01-02T15:08:38.973+0100] CommonDataPathForCurrentUserPersisted: C:\Users\Daniel\.affinity\Common\2.0
[2024-01-02T15:08:38.973+0100] CommonDataPathForCurrentUserPersistedBuildInvariant: C:\Users\Daniel\.affinity\Common\2.0
[2024-01-02T15:08:38.974+0100] CommonDataPathForAllUsers: C:\ProgramData\Affinity\Common\2.0
[2024-01-02T15:08:38.974+0100] TempPathForCurrentUser: C:\Users\Daniel\.affinity\Publisher\2.0\temp
[2024-01-02T15:08:39.604+0100] Skipping check for updates (no update available in recent check)
[DXCore] Found 2 adapters
NVIDIA GeForce RTX 2070
	Version: 31.0.15.4629
	IsHardware: Yes
	Supports D3D12 Feature Level 12.0: Yes
	HardwareID: PCI\VEN_10DE&DEV_1F02&SUBSYS_10710000&REV_A1
	LUID: 0x114C9
Microsoft Basic Render Driver
	Version: 10.0.19041.3636
	IsHardware: No
	Supports D3D12 Feature Level 12.0: Yes
	HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00
	LUID: 0x12137
[DXGI] Enumerating adapters
NVIDIA GeForce RTX 2070
	HardwareID: PCI\VEN_10DE&DEV_1F02&SUBSYS_107138420000&REV_A1
	LUID: 0x114C9
Microsoft Basic Render Driver
	HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00
	LUID: 0x12137
[OpenCL] Found 1 platforms:
Name: NVIDIA CUDA
	Vendor: NVIDIA Corporation
	Version: OpenCL 3.0 CUDA 12.3.106
[OpenCL] Found 1 devices for platform NVIDIA CUDA:
NVIDIA GeForce RTX 2070
	Vendor: NVIDIA Corporation
	Version: OpenCL 3.0 CUDA
	Integrated: false
	Detachable: false
[2024-01-02T15:08:41.879+0100] 	Installed
[2024-01-02T15:08:45.518+0100] TabletContext::Create: original queue size is 50
[2024-01-02T15:08:45.518+0100] TabletContext::Create: new queue size is 128
[2024-01-02T15:08:45.520+0100] Content migration already offered previously
[2024-01-02T15:08:49.184+0100] Attempting to create Direct3D device on default adapter
[2024-01-02T15:08:49.287+0100] Setting screen DPI to 93.1575931232092 (scale = 1.0)
Begin check for updates...[2024-01-02T15:09:28.187+0100] ...check for updates completed
[2024-01-02T15:09:28.193+0100] No update is available.
Begin check for updates...[2024-01-02T15:12:22.485+0100] ...check for updates completed
[2024-01-02T15:12:22.486+0100] No update is available.

 

[Motljus]

Never mind. The 2.3.0.2165 beta version seems to have fixed this issue, so I can rely on the beta version in the meantime.

[walt.farrell]

51 minutes ago, Motljus said:

Never mind. The 2.3.0.2165 beta version seems to have fixed this issue, so I can rely on the beta version in the meantime.

The 2.3 retail and beta versions are the same code, given that they have the same build number (.2165).

Does your problem happen in all documents, or only one specific document?

Have you tried starting the retail version while holding the Ctrl key, and resetting the application? Just leave the default items checked and click Clear. This should be fairly non-destructive (brushes, etc, will be retained) but it will reset your Studio preferences/arrangement.

[Motljus]

One might think that, but the regular release 2.3.1 still hangs (although I realized that I can escape by pressign "Esc" to continue editing, since it seems to escape the invisible dialogue that hangs the client).

The only working solution is to keep using the beta client 2.3.0.2165 beta, where the hyperlinking still works. I wonder if the documents have been made incompatible with the 2.3.1 release version perhaps?

[Motljus]

I got an idea that the popup window to edit the hyperlink might simply be off screen in my 2.3.1 installation, since pressing Esc made it possible to continue editing.

By using the Windows+Arrow keys I managed to navigate the window back onto screen again and solve the issue. Wonder how it got there in the first place, but now it works again.

[walt.farrell]

21 minutes ago, Motljus said:

Wonder how it got there in the first place, but now it works again.

Do you ever use multiple monitors? If so, you probably last used that dialog on a monitor you don't currently have attached and powered on.

[Motljus]

I do, but normally windows aren't stuck outside any of the monitors.

Anyhow, problem solved, I guess.