Publisher Closing down V1.9.2.1035

[andersp5]

Hi, can anyone advise please, is there a known crashing problem with Publisher Version V1.9.2.1035 with Windows 10 Home V21H1 OS Build 19043.1110?

I came to use publisher V1.9.2.1035 today and on opening a new blank document (A4), the page appeared, there was a slight delay, then the programme just crashed ie. Closed down. I searched the forum and someone suggested to untick OpenCL from the edit, preferences menu.

However, if I just open the programme and do nothing else, then go to Edit then Preferences, nothing appears and the programme crashes after a slight delay. I simply can not use this version now, any ideas?

I have restarted my PC and tried again with the same result. I am now thinking of either going back to the previous version or deleting this version and re-loading it or try the latest Beta perhaps

[macsnapper]

That happened to me quite a lot with v1.92 so I reinstalled v1.90

 

[andersp5]

Thanks for the reply, I was going to do that myself today but decided I would try the latest Beta v1.10.0.1115 first, would you believe it works perfectly, so far!!

I loaded and manipulated a previous document, tried the Edit then Preferences etc it opened OK and it did not crash, however time will tell if it is anywhere near stable but at least I can now use it until the latest release is finalised.

So, something has definitely changed from V1.9.2.1035 to this Beta...I wonder what? 

[Gabe]

Hi both,

The main thing that's changed was OpenCL. Which was quite problematic for some GPU drivers. You can have a look here 

 

[macsnapper]

Thanks Gabe

I had disabled OpenCL but still had crashes.

I have it disabled in v1.90 as well, and it's working well.

Maybe I should look at the beta andersp5 is looking at but I may wait until it's no longer beta, as I don't have a big project on right now.

 

[Gabe]

Can you attach some crash reports? https://forum.affinity.serif.com/index.php?/topic/98904-faq-where-to-find-crash-reports/ it must be down do the drivers. 

[macsnapper]

Whew -who knew there was a record like this...

As I say I don't have any big project going right now, so I'm not going to sweat about it, but you may find these useful?

e52d2090-b965-45a3-8c29-dd063a7d1684.dmp e104f8a8-c869-4fed-b670-ad74aa695877.dmp e0577c04-9970-4247-8364-d44bed82878f.dmp f5ef405e-1b1e-4bbb-b759-a28f9b9739ec.dmp f4147d62-2e6f-43de-acce-0480b6cea401.dmp fc6b505f-9f75-40eb-b497-f7b332b4d8e3.dmp 3d2fb64a-45dc-4e10-85f7-a91f14230888.dmp 5c8f7afa-f2c0-4f3f-8a37-28ba13edc949.dmp 9b3908f5-d9c6-422e-a26d-8ea5badc7877.dmp 17e2b0a6-98e0-4d09-97a0-893901a3533b.dmp 39e69066-5e2a-47eb-985a-af148756e019.dmp 42b88da2-1866-4127-8427-925eb87d8951.dmp 44d58286-6b8d-459f-a219-1c2f34d1b7dc.dmp 63f8ebb6-f705-4992-9b17-274a1d5c150e.dmp 78e1f37d-edc9-434e-961f-b0e765ed4347.dmp 96c39dea-7481-44a5-bbcb-74d43f207fb3.dmp 334b9f45-48f0-404c-8215-85916a736b59.dmp 419e8324-8cdb-4235-8755-70298d4328c9.dmp 477b7674-1617-4e0c-a880-5c954e851c91.dmp 4233b626-f8a7-459d-94c8-48281c208932.dmp 56980fe1-e7eb-4c23-a611-d084dbf1821f.dmp a7db757f-bdd7-45c9-a48a-5198810601f2.dmp b8d95708-1412-4f9c-a5a7-826a3315079d.dmp b9ff59ad-2f39-4ac9-96c5-7a3bbd90ff4e.dmp b793b53b-7d34-4e5f-939c-e00329522f33.dmp c0122b21-c56c-4eda-a573-046f51acc1a0.dmp d006a17c-e640-41a9-9be5-2257f3edde91.dmp e0cb13f6-9b37-4e3b-bbf4-67f696e3229e.dmp

[Komatös]

@macsnapper I suggest you to update the GPU drivers. And also a short check of windows system integrity with sfc.

To run the check press Windows key + R, type cmd in the field, hold shift + ctrl and klick OK or press enter.

In the command promt windows type sfc /scannow and press enter.

[macsnapper]

thanks Komatös

sfc showed no integrity errors and display adaptor intel graphics hd 520 driver is up to date.

Not to worry, I'll wait for the next publisher update to come out of beta and give that a try.

cheers