Windows 10, 2 x monitors crash on startup

[PI2020]

1. Version 1.8.5.703
    
2. Can reproduce on demand!
    
3. Happens when opening Publisher by clicking on an .afpub file and when opening the application from a shortcut or .exe.
    
4. Windows 10.0.19042. GPU = Nvidia GTX 960, driver version 457.30 (DCH)
   
   The application begins to open, after the "loading fonts" message the panels/palettes begin to appear (positioned on monitor #2, above monitor #1) . At this point it slows to a crawl. One palette every few seconds. Eventually, it will finish startup, the main screen will flash up on monitor #1, and then the whole thing crashes out. Crash logs are being automatically uploaded according to the settings, and in the log file after parsing all 53 of the ,icc files , it states:

   Imported
       -- 700.9904ms

   That's the last line of the log.... Repeat the process, and the application does the same thing, but doesn't crash out and is usable. (Regardless of if it's opened via a document or directly as an application.)

5. Software that could be involved? Printers Apprentice (not running), VirtuaWin 4.5

6. What seems to have prompted the change, is using a 2nd monitor - namely splitting the UI so that panels/palettes sit above in monitor #2 and main UI and document are below on monitor #1.

 

Also, I've just checked the log file again, after a successful start, and it contains what seems to be a more complete entry. The text below was missing previously:

TabletContext::Create: original queue size is 50
TabletContext::Create: new queue size is 128
Attempting to create Direct3D device with adapter NVIDIA GeForce GTX 960
Setting screen DPI to 96.0472673559823 (scale = 1.0)
Exit

 

Any more info needed, please let me know.

Log.txt

[Gabe]

Hi @PI2020,

Welcome to the forums. 

Can you attach a crash report? You should find them in: %appdata%\Affinity\Publisher\1.0\CrashReports\reports

Does it crash without VirtuaWin 4.5 installed?

[PI2020]

Hi,

 

I haven't tried without VirtuaWin - I've been using it for years, it's always been fine, even with Publisher Beta. I'm 99.9% sure it's since I've moved the panels/palettes to the 2nd monitor.

Crash report attached.

Thanks, kind regards, Paul

343f36ad-a4f7-48bf-993c-b626fc3cdba3.dmp fd5e4d6e-44ed-4e29-a391-7faf3234b053.dmp fb9cc541-e606-4409-80bd-3c4fc29e21dc.dmp dabeb67c-647b-4fc4-8ced-62c0d179baed.dmp

[Gabe]

Would you be able to try the following for me please so I can get a bit more information from your crash reports. 

Go to C:\Program Files\Affinity\Publisher\ and open the Publisher.exe.config file inside a text editor. Could you add the following line between the <runtime></runtime> section of the file:

<ZapDisable enabled="1" />

This should make your file look similar to this:

Once that has done, could you run Publisher up and make it crash. Attach the new crash report and we can have a look. 

[PI2020]

Hi,

Done and done!

Cheers, Paul

2c866e70-00de-428b-84c9-cad6af8acacc.dmp

[Gabe]

Nothing helpful here either  . Maybe have a look inside Event Viewer? Check this post for how to save the log