Bug 389248

Summary:	Lokalize segfaults when searching via Translation memory
Product:	[Applications] lokalize	Reporter:	Andrej M. <andrej.mernik+bugs>
Component:	translation memory	Assignee:	Simon Depiets <sdepiets>
Status:	RESOLVED FIXED
Severity:	crash	CC:	sdepiets
Priority:	NOR	Keywords:	triaged
Version First Reported In:	2.0
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Andrej M. 2018-01-20 12:12:18 UTC

Dear developers,

When searching the translation memory in Lokalize from Apps 17.12, the application crashes with Segfault (core dump). The crash doesn't happen for first search, but after that, it happens every time until system restart. Everything else in the program works, even translation suggestions via TM.

The translation memory was emptied and recreated, but didn't help. The contents of TM are fully readable via SQLite browser, no errors were found.

I couldn't reproduce this bug in latest Kubuntu 18.04 (Apps 17.08) or Debian Stretch (Apps 16.08).

Best Regards,
Andrej Mernik

Comment 1 Simon Depiets 2018-08-13 09:43:22 UTC

Could you put your translation contents/translation memory accessible so that we can try to reproduce this issue ?

Comment 2 Andrew Crouthamel 2018-09-28 03:37:29 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Simon Depiets 2018-09-28 03:43:27 UTC

This was a concurrent thread access issue, I actually solved it from another bug and forgot to close this one.

https://phabricator.kde.org/R456:2b183be33e93ffd30d4d9238704051c971ede0b4