| Summary: | crash when searching for "Add\\." in TM | ||
|---|---|---|---|
| Product: | [Applications] lokalize | Reporter: | Alexander Potashev <aspotashev> |
| Component: | general | Assignee: | Simon Depiets <sdepiets> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | freekdekruijf, lasse.liehu, sdepiets, wantoyek |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
video
manage TM dialog |
||
|
Description
Alexander Potashev
2018-08-27 22:47:16 UTC
Hello Alexander, Can you reproduce this bug ? Retried it two times now, it was reproducible. Lokalize package version: 18.04.3-1.fc28 Can you send your translation memory ? It should be in .local/share/lokalize/*.db A screenshot of the research just before clicking the search button would also help ensure we use the same parameters Project opened in Lokalize: svn+ssh://svn@svn.kde.org/home/kde/trunk/l10n-kf5/ru/index.lokalize Data from .local/share/lokalize: https://mega.nz/#F!GOxlHYZL!h7O3n13F9nlSvvhcksxesQ default.db and kde-ru.local were modified months ago, so I don't think these are used by Lokalize. Created attachment 114676 [details]
video
It's strange that you don't have any translation memory selected when you switch to the Translation Memory tab. What do you have in the "Manage Translation Memories" dialog ? https://imgur.com/a/RDTl7To Created attachment 114699 [details]
manage TM dialog
I can select "kde-ru" in TM, it still crashes when searching for the same. I've installed a fresh Fedora in russian on a virtual machine and can't reproduce. Two last things to try, can you send over your .config/lokalizerc and the result of ls -l /lib64/libsqlite3.so.0 /lib64/libpthread.so.0 Disregard actually I was able to reproduce with any chain I can only reproduce by spamming the Search button very quickly. Could you launch lokalize from the console and send over the log messages ? I think I was able to fix my issue which was slightly different (only triggered randomly or when spamming) but probably related. I suspect the problem is the multithreading access to the database provider between the thread that launches the queries and the thread that reads the result. I added some mutexes and cleanup of previous queries and I'm not able to make it crash anymore. It seems the rework done on QSqlQueryModel in Qt 5.10 and Qt 5.11 might be the cause. https://github.com/KDE/lokalize/commit/2b183be33e93ffd30d4d9238704051c971ede0b4 Cannot reproduce anymore with the current git master. Thanks! *** Bug 400149 has been marked as a duplicate of this bug. *** Lokalize 2.0
KDE Frameworks 5.50.0
Qt 5.11.2
Distribution: openSUSE Tumbleweed 20181018
packet version: 18.08.2-1.1
Yesterday a new version of lokalize became available and was installed.
Same search as in 400149
> LC_ALL=C lokalize --project=vertalingen/KF5trunk.lokalize
QStatusBar::insertWidget: Index out of range (5), appending widget
Trying to convert empty KLocalizedString to QString.
org.kde.kross.core: Action::setInterpreter: interpreter not found: "python"
Segmentatiefout (geheugendump gemaakt)
I started as above. On another console I started gdb and attached to that lokalize, entered continue. I did the same search, which succeeded. I was able to repair some words, which was the objective for the search, and finally finished my work.
I got a lot of messages from gdb trying to load debuginfo files, even tried to install these, which fails because I logged in as a non-root user.
Starting lokalize again as above, not using gdb and doing again the same search results in the same error message above. So currently the problem is always reproducible.
v18.08.2 does not include the bugfix. Simon, could you please backport the bugfix into branch "Applications/18.08" to make it available in 18.08.3? I think there's just too many changes on the master currently that are not bugfixes to do that (In reply to Simon Depiets from comment #18) > I think there's just too many changes on the master currently that are not > bugfixes to do that This is not a problem, you can still use git-cherry-pick https://git-scm.com/docs/git-cherry-pick *** Bug 400354 has been marked as a duplicate of this bug. *** I made too many modifications of the code base before that fix so I gave up on the cherry picking (especially this close to 18.12). Just tried to reproduce after the newest update of openSUSE Tumbleweed. Lokalize version 2.0 KDE Frameworks 5.52.0 Qt 5.11.2 (gebouwd tegen 5.11.2) Still reproducable. (In reply to Freek de Kruijf from comment #22) > Just tried to reproduce after the newest update of openSUSE Tumbleweed. > Lokalize version 2.0 > KDE Frameworks 5.52.0 > Qt 5.11.2 (gebouwd tegen 5.11.2) > Still reproducable. please retest with lokalize-18.12.0 (not released yet) Can you check with 18.12 ? I'm pretty sure it's fixed there It's OK now. Thanks. |