I made 4 new tests this evening with the same set of pictures and the same exact parameters. APG crashed once again, but normally terminated the three other runs.
The crash happened just after APG saved the HDR file, without letting me the time to save the .pano file.
There is another anomaly: in the first test of the series, APG produced a .hdr file which is completely different from the others. When looked in Phonomatix, it appears very clear (exactly like the least exposed of the braketed images), and is actually unexploitable. The two other .hdr files I obtained seem correct when opened in Photomatix.

The net is that I couldn't identify a particular pattern that causes APG to crash. It seems to happen randomly (2 times out of 5 runs), and always when the .hdr is being filed, or just after it is filed. And, considering the .hdr files seems to be incorect from time to time, my humble opinion is that there is something wrong with the generation and writing of .hdr files.

I'll make further tests tomorrow.

Edit: I just uploaded my picture and details of my four runs in a "Olivier Marmotte06 - Crash APG.zip" file on your FTP server.
There is a readme file explaining what I did.
Hope that can help

Olivier

Last edited by Marmotte06 (2011-12-20 22:17:28)

So far it works, I will make bigger HDR panos tomorrow to stress this version, and let you know the results.

Thanks for the quick fix, and Best Regards

Olivier

Do you have avast antivirus ?

I totally agree with you and didn't ask that.

Ok, new tests: I think there might be two different problems....

First, I went to the APG general parameters (main menu), and I noticed that, by defaut, the GPU option was actuvated (I don't remember setting it myself). I desactivated it and... All the crahes I reported in my latest posts, i.e. since I got the APG with the new QT, disapeared.
I could assemble a small HDR pano without any problem.

I then tried a bigger one (96 jpegs), and I could properly assemble it end-to-end. APG produced a .hdr which is exploitable in Photomatix, but... eventually crashed on the "Save as" dialog box when trying to save the .pano file afterwards.

So, I believe there are two distinct problems:
1) The GPU option in the editor, that causes a lot of crashes.
2) The File dialog boxes, that happen to crah time to time (not always).

Regarding the GPU, I have an AMD Firepro 5800 graphic card, with the latest device driver available from AMD.com (version FirePro_8.85.7.2_Win7x64_125182), my screen is a NEC PA 241W (1920x1200 resolution) connected to the card by DisplayPort, but I am still in 8 bit/pixel color depth (not 10).

Olivier

Hi Alexandre,

As mentioned in my previous message dated "2011-12-20 20:12:10", I have already uploaded my pictures in a "Olivier Marmotte06 - Crash APG.zip" file on your FTP server.

Let me know whether you need more info.

I understand your thoughts regarding the GPU option, but the reality is that when this option is anabled APG is a plain disaster, crashing at any time as soon at the editor is active, and that disabling the GPU option makes it workable, at least until saving the final files.
And, BTW, I saw on the forum another post mentioning exactly the same behavior with the GPU option, which should certainly not be enabled by defaut. (I don't care about this option, I don't see what it brings to me).

At last, please note that I am using a Firepro professional graphic card, which has a different Catalyst device driver than the regular AMD/ATI graphic cards. Did you test that the APG GPU option works fine on such a setup ? You'll never be able to test all the configs on the market, this is why you should let the GPU option disabled by default, like in previous versions of APG. You are taking risks for nothing.

Olivier

Last edited by Marmotte06 (2012-01-05 08:30:47)

AlexandreJ wrote:

So, it's something else. It could be related to another issue posted in some other thread : issues on Windows 7, 64bits.
This bug happens regularly when using system dialog box ( file open, file save, folder browse, etc ). It hangs during those operation and sometimes crash.

Note : I guess, you have the latest catalyst drivers for your GPU installed, right ?

Well, I saw your other post regarding forums where users complain about crashes in file system dialogbox. Bear in mind that I (and others) have been using Win 7 x64 for a while now, opening and saving thouthands of files with several other apps (32 bits and 64 bits) without problem. So, if there is really a problem with these dialog box, it's rather a problem regarding how some applications use (or mis-use) it...

I was going to answer you that I use the latest driver for my Firepro card, but I just checked on the AMD site and they published a new version late december. I will install it tonight and check. The Firepro V5800 card is based on the HD5770 GPU.
That being said, I didn't realize you were using OpenGL. I checked the AMD release note for the Firepro driver, it supports Open GL 4.1 for my V5800 card, but I see there is a more recent version of Open GL (4.2) supported by the latest cards. Is OpenGL 4.1 ok for you ?

Olivier

Good Evening,

I just installed the latest driver from AMD for my Firepro card (version 8.85.7.3 dated Dec 19th 2011):
- Laugh APG, set the GPU option on, load some braketed images, set a couple of options, lauch detection, open the editor, do a -0.3 degree horizon correction -> instant crash
- Relaunch APG, deactivate the GPU, close
- Relaunch APG, reload the images and so on, the editor doesn't crash anymore. But.... try to close it, it asks whether I want to save the project, I say Yes, -> instant crash !

Conclusions: the "GPU crash" is very solid, and the "Save dialog box crash" is relatively easy to produce (you don't even need to compute any pano)...

Just a question: in the "Options Editeur->Nombre de Processeurs", I have defined "Multi-cores" with "4" cores, although I have hyperthreading enabled and the defaut option after APG install was "8" cores. Is that a problem ? (I remember reading in this forum that APG was not actually using the virtual cores).

Olivier

Last edited by Marmotte06 (2012-01-06 21:43:00)

Hello, I installed the new 2.6.1 RC1
The editor still crashes when the GPU is enabled, but less frequently, I could do some editing without crashing imediately as before.

Also, the 2.6.1 RC1 still crashes on the save dialog box.
I used CCleaner to deactivate Avast loading, with no effect, AGG still crashes when saving the project.
I then deactivated Logitech SetPoint, no effect -> crash
then the Catalyst Control Center, and... so far no crash after many saves, but I need to make more testing to confirm...

I would like to try the "crash dump analysis" version you mention in http://www.kolor.com/forum/t13891-autop … h-analysis , but the link to download it seems down/broken tonight.

Olivier

Last edited by Marmotte06 (2012-01-12 22:58:53)

I installed AutopanoQT_x64.exe and tried:

So far I couldn't reproduce the GPU crash with that version. In my past developer carrier, I remember crashes disapearing with debug versions of the code because of multitasking behaving differently in debug versions (because debug versions are usually slower), or because debug versions were compiled with less agressive optimization options, which avoided some compiler bugs when performing complex optimizations. I guess you are using C or C++, and that you are compiling with maximum optimization options. I suspect this could be the cause of some of your problems... Perhaps you could post an executable with no optimization at all, and let us see what happens...

The save dialog box crash is still there, and easy to reproduce. However, I followed your procedure but it my C:\Users\xxxxxxx\AppData\Local\Temp\ directory, the only file I could find before closing the windows crash dialog box is WERA5D0.tmp.WERInternalMetadata.xml , and this file doesn't contain much information. I have never seen the xxxxx.tmp.appcompat.txt and xxxxx.tmp.mdmp files, even transient.

Olivier

Marmotte06 wrote:

Frankly, I wonder how Kolor can decide to label "final" a software with such a problem, even though Avast might not be innocent in its cause.
In all the IT industry, this is known as a "severity 1" problem, and a product is not released with such a known problem.
I am bored of APG. I will not renew my license when the 3.0 appears.

Olivier - i can´t imagine that´s an APG issue. But i´m on Macs . . . so i don´t have this kind of problems (and that´s why i use Macs )

The problem you describe would occur with lots of other users if it was an APG issue. Does it? No.

I don´t know what "Avast" is - but if it produces troubles: get rid of it. Correct made softwares don´t crash apps.

best, Klaus

AlexandreJ wrote:

- All have Avast antivir installed.

I confirm that the problem is linked to the presence of Avast. I replaced it with MS Security Essentials (which is not too bad), and APG hasn't crashed anymore.
This doesn't mean Avast is responsible. I do not see why the presence of a particular antivirus should affect your application so badly, unless APG behaves abnormally when accessing directories. Is that your code that manage the dialog boxes, or some GUI framework (e.g. QT) ?

Olivier