Aftershot Pro Crashes if i delete Photos

[cluhn]

If i delete Photos in the Catalog or in de Filesystem Aftershot Pro crashes every first or third photo.. It is really annoying.

I use Aftershot Pro Version 1.0.10 64-bit under Ubuntu Linux 11.10 (the last months) and since some days under 12.04.

The error exists since i use ASP. Are there any Logfiles that i can send to the developers that are usefull to analyse the Problem? Do someone know this Problem and can help me resolve it?

[afx]

See if you can spot anything interesting in the AfterShotPro.log file in your AS user directory.
You might want to post the last 20 or so lines here. If that has nothing interesting, strace would be the next option.

cheers
afx

[cluhn]

Hi,

there is not much to see in the logfile.. There are only the files that being "trashed" and then 75913.761: Nuance: HOTNESS CHANGE..

No one else seems to have this Problem. :/

strace ends with the output "--- SIGSEGV (Segmentation fault) @ 0 (0) ---"

[afx]

Is the Nuance entry the last one before the segfault? Are you sing the latest version of Nuance?

cheers
afx

[cluhn]

So i disabled Nuance and deleted around 100 photos with no problems. But suddenly it crashes again while deleting a photo, from now on it is crashin every time i delete a photo. The aftershotpro.log says nothing.. Here is the output from strafe (removed my username):

Code: Select all

_llseek(49, 24, [24], SEEK_SET)         = 0
read(49, "\0\0m\7\0\0\0\0\0\0#\"\0\0\7W", 16) = 16
fcntl64(49, 0xd /* F_??? */, 0xffe12974) = 0
gettimeofday({1336308252, 76486}, NULL) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2309, ...}) = 0
fcntl64(49, 0xd /* F_??? */, 0xffe12214) = 0
fcntl64(49, 0xd /* F_??? */, 0xffe12214) = 0
fcntl64(49, 0xd /* F_??? */, 0xffe12214) = 0
access("/home/user/Bilder/AfterShot Pro Catalogs/Eigener Katalog/base-journal", F_OK) = -1 ENOENT (No such file or directory)
fstat64(49, {st_mode=S_IFREG|0644, st_size=9340928, ...}) = 0
_llseek(49, 24, [24], SEEK_SET)         = 0
read(49, "\0\0m\7\0\0\0\0\0\0#\"\0\0\7W", 16) = 16
fcntl64(49, 0xd /* F_??? */, 0xffe121f4) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
Process 8899 detached


Maybe the "base-journal" is the problem? This do not exist..

[afx]

The journal is only a temporary file...
But I suspect your catalog is hosed.
Best recreate it.

cheers
afx

[photoalexis]

I had the same problem, but i uninstalled ASP and re-installed it and it fixed the issue. The catalogs and all keywording was not affected.

[cluhn]

Hm.. i uninstalled ASP and recreated the catalog and i have the same error..
I deleted the configuration directory in my homedirectory and the configuration was still available after reinstallation. Where ASP stores the configuration?

[afx]

I deleted the configuration directory in my homedirectory and the configuration was still available after reinstallation. Where ASP stores the configuration?

What configuration?

Your user folder stores batch settings, defaults, presets, the cache and a pointer to the catalogs.
The layout changes are stored in the appropriate Qt places, which on Windows is in the registry, on Linux somewhere under ~/.config and PLIST on MacOS where I forgot the exact location...

cheers
afx

[bee]

I have what sounds like the same symptoms. After deleting a couple of photos it will crash. Might crash on the first photo, or might make it to the 3rd or 4th before crashing. I am running the current aftershot trial on windows 7. After uninstalling aftershot, deleting the catalog, and running CC registry cleaner. I reinstall and have the same problem,this time not using the catalog function.

[kaymann]

I deleted a couple of files and got a C+++ error on the next restart. If I ignored the C+++ error everything continued to work fine. If I clicked OK or Ignore or Cancel, ASP shut down. If I stay in file system no C+++ error. It took a catalog delete and new catalog to fix...

It seems fairly consistant delete files/empty folders and problems will show up. Already reported to monkey.

[cluhn]

Hi,

my problem seems to be resovled, sorry for the late answer but i had to test it for a longer period..
Ich resetet the size of my cache to 1024mb and the problem never happend again. (I configured 2048mb for months ago..)