Bug 338358 - Segmentation fault in libthread_db.so.1 saving jpeg in new version after editing
Summary: Segmentation fault in libthread_db.so.1 saving jpeg in new version after editing
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Sqlite (show other bugs)
Version: 4.1.0
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-18 16:18 UTC by Yuri Ingultsov
Modified: 2021-04-04 14:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.3.0


Attachments
Backtrace, OS/KDE details and description (15.91 KB, text/plain)
2014-08-18 16:18 UTC, Yuri Ingultsov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Ingultsov 2014-08-18 16:18:58 UTC
Created attachment 88307 [details]
Backtrace, OS/KDE details and description

1. I get opend jpeg in editor
2. I added resize & sharpen filters
3. pressed "close editor" and then select save as new images
4. moved new verrion of image to another albut

repeat the steps above for several  images 2-5 time and it will crashed
Comment 1 caulier.gilles 2014-08-18 18:38:57 UTC
Thread 1 (Thread 0x7f2e87baeac0 (LWP 5421)):
[KCrash Handler]
#6  0x0000000f00000030 in ?? ()
#7  0x00007f2e6ace8dac in sqlite3MemCompare (pMem1=pMem1@entry=0x7fff56b27100, pMem2=<optimized out>, pColl=0x1e240c8) at sqlite3.c:60484
#8  0x00007f2e6ace8f63 in sqlite3VdbeRecordCompare (nKey1=37, pKey1=0x45a7ea3, pPKey2=pPKey2@entry=0x7fff56b27400) at sqlite3.c:64162
#9  0x00007f2e6acfd579 in sqlite3BtreeMovetoUnpacked (pCur=0x5433cf0, pIdxKey=0x7fff56b27400, intKey=0, biasRight=<optimized out>, pRes=0x7fff56b273f0) at sqlite3.c:55077
#10 0x00007f2e6ad259c5 in sqlite3VdbeExec (p=p@entry=0x6d5c958) at sqlite3.c:70168
#11 0x00007f2e6ad2ded7 in sqlite3Step (p=0x6d5c958) at sqlite3.c:64828
#12 sqlite3_step (pStmt=<optimized out>) at sqlite3.c:64894

It's the Sqlite BC problem...

Gilles Caulier

*** This bug has been marked as a duplicate of bug 329697 ***
Comment 2 caulier.gilles 2021-04-04 14:29:34 UTC
fixed with #329697