Bug 483721 - Crash when searching translation memory
Summary: Crash when searching translation memory
Status: RESOLVED FIXED
Alias: None
Product: lokalize
Classification: Applications
Component: translation memory (show other bugs)
Version: 24.02.0
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Simon Depiets
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-16 06:15 UTC by fin-w
Modified: 2024-12-02 16:51 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Crash on searching source strings in translation memory (40.12 KB, text/vnd.kde.kcrash-report)
2024-03-16 06:15 UTC, fin-w
Details

Note You need to log in before you can comment on or make changes to this bug.
Description fin-w 2024-03-16 06:15:50 UTC
Created attachment 167292 [details]
Crash on searching source strings in translation memory

SUMMARY
When I search in a translation memory (TM), Lokalize crashes immediately. I have attached crash info from DrKonqi.

STEPS TO REPRODUCE
1. Make project with an xliff file in it, add the translations in the xliff file to the translation memory for that project
2. Search for a source string

OBSERVED RESULT
Lokalize crashes if the search string is the string "mass" or "mas" BUT NOT "ssssss" or "ma" or "as", for my translation memories. Other translation memories work with all of these strings without crashes, they crash in different (but similar) cases.

EXPECTED RESULT
No crash. Results where appropriate.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Comment 1 wojnilowicz 2024-12-02 16:44:25 UTC
You get SIGABRT here. I can confirm crashing but with SIGSEGV. I noticed that it happens because one thread inserts to a database while another one fetches from it.
Comment 2 Albert Astals Cid 2024-12-02 16:51:17 UTC
Please try this again once 24.12.0 is released since i made quite a few fixes in this regard. If it still crashes please reopen