Topaz Gigapixel AI Update 8.3 The program closes and does not work

Topaz Gigapixel AI Bugs and Issues
22

I should note, my problem is in Photo AI, not Gigapixel.

23

Same problem here. loading an image shuts down the program-Gigapixel 8.3 3/21

24

thanks so much for the link!

1 Like
25

Same here. Just installed Gigapixel 8.3.1 and it crashes opening up any image. Tried big and small images. Tried webp, png, and jpg. Nothing works.

It looks like all the versions on the site are 8.3.1. I do not see 8.2.2 anywhere.

EDIT: Just found it on the forum here:
https://downloads.topazlabs.com/deploy/TopazGigapixelAI/8.2.2/TopazGigapixelAI-8.2.2.msi

26

They changed it to 8.3.1 there now. There is a link in the forums to 8.2.2 though.

27

However, the error remains according to someone who tested it.

28

Hello everyone, Topaz is asking me for some tests and files from my machine (application logs).
The last test was with Windows administrator permissions, but that didn’t solve anything either, meaning the problem persists and is something else.
They are trying to figure out what’s going on.
If I find out anything else, I’ll share it.

1 Like
29

I’m having the same issue.

it crashes after selecting an image at “Detecting Faces”.
no way to disable it or change the parameters, before it starts doing its job

Windows 11 Pro 23H2 OS Build 22631.5039 (latest)
NVIDIA GeForce RTX 4090
CPU 13th Gen Intel(R) Coreℱ i9-13900K

Gigapixel 8.3.1, done all the recommended steps.

In the [Date-TIME].tzlog file is no real information on the file, process or crash.
only on startup, folder and system specs

I can provide the crashpad report if needed

1 Like
30

i found this in win events

Nom de l’application dĂ©faillante : Topaz Gigapixel AI.exe, version : 8.3.0.0, horodatage : 0x67db4c3d
Nom du module défaillant : colorio.dll, version : 0.0.0.0, horodatage : 0x67db4ae9
Exception code: 0xc0000005
Fault offset: 0x0000000000012560
Identifiant du processus défaillant : 0x2354
Heure de dĂ©but de l’application dĂ©faillante : 0x1DB9A51CBBB6D61
Chemin de l’application dĂ©faillante : C:\Program Files\Topaz Labs LLC\Topaz Gigapixel AI\Topaz Gigapixel AI.exe
Chemin du module défaillant : C:\Program Files\Topaz Labs LLC\Topaz Gigapixel AI\colorio.dll
ID du rapport : 8c6dda84-1ee8-47fd-bba5-518872045154
Nom complet du package défaillant :
Package dĂ©faillant – ID d’application relatif :

2 Likes
31

Merci pour l’info, guy.elissalde ! Je l’ai dĂ©jĂ  transmis au support pour qu’ils le vĂ©rifient.

Thanks for the info, guy.elissalde! I’ve already sent it to support for verification.

32

I just received this message from support.

I had already installed version 8.2.2 because I needed it


Hi Collazo,
A newly confirmed issue with Gigapixel v8.3.0 and v8.3.1 is causing crashes and errors. It’s not just your system.

We are working on the fix right now, and it should be out within 24 hours!

If you need a fast solution, you can install Gigapixel v8.2.2

33

8.3.2 does not fix this issue as well.

1 Like
34

I updated the program to version 3.2, but the same issue persists. Unfortunately, it was not resolved.

:man_facepalming:

1 Like
35

Still crashes without error messages when I try to open any kind of images. No matter if is a jpeg, tiff, or something else. It just closes itself without a notification. 13th Gen Intel(R) Coreℱ i7-13700KF 3.40 GHz with Nvidia RTX4070. Why has this Topic the status: “This topic has been solved” In my opinion nothing is solverd so far
 :frowning:

36

Lol, got excited when I saw it was a new update. Upgraded to 8.3.2 and just like everyone
same crash, no matter what image I load. Very frustrating
we’re all paying for a subscription to take advantage of new improvements and this happens


Hoping the team REALLY backtests a new version before it gets released. Because it seems like nothing was fixed from the last update.

Off to uninstalling/reinstalling 8.2.2 and wasting another hour of my life.

1 Like
37

What happened is that, at the time, they mentioned that the update would come with the fix, and I believed it, so I marked it as solved, but in the end, it wasn’t.
Next time, I’ll keep it in mind—until it’s truly fixed, I won’t mark the option.
Regards.

1 Like
38

Alright, I figured out how to remove the “solved” mark.
I won’t put it back until they fix it.
Regards.

1 Like
39

I just received this support notice:

"Hi Collazo,
Thank you very much. We are working on this as I write to you. I will get back to you as soon as we have it fixed. Thank you so much for sending me the logs.

I’m sorry this has been such a headache. Hopefully, the devs will have it fixed soon.
Kind regards,"

So they are working on the solution to the problem.

1 Like
40

Same with me.

1 Like
41

8.3.3. do the trick for me. Finally no more crashes! :slight_smile: