Download it now!
Bug 103061 - Assertion failed when right-clicking an incorrectly spelled word in Writer in debug build
Summary: Assertion failed when right-clicking an incorrectly spelled word in Writer in...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Linguistic (show other bugs)
(earliest affected)
Hardware: All Windows (All)
: medium major
Assignee: Not Assigned
Depends on:
Blocks: Spell-Checking
  Show dependency treegraph
Reported: 2016-10-09 07:38 UTC by Aron Budea
Modified: 2017-01-19 04:33 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Aron Budea 2016-10-09 07:38:35 UTC
Have a debug build of master branch.
Add English dictionaries to 'share/extensions/dict-en' if it's not there already.

1. Start Writer.
2. Switch text language to English (USA).
2. Type an incorrectly spelled word, like "tset".
3. Right-click the word.

=> debug assertion failed
"Expression: vector iterator not decrementable"

Occurs in line:
int count = pMS->suggest(&suglst, aWrd.getStr());

So, somewhere inside hunspell. Not sure why I can't debug into it.

Build ID: d4936e876b1b965505ee2e82efaa35eef65d2135
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
Locale: hu-HU (hu_HU); Calc: group
Comment 1 Aron Budea 2016-10-09 07:44:03 UTC
Oops, numbering of steps is a bit messed up. Also, I forgot to add that "Automatic Spell Checking" needs to be enabled.
Comment 2 Buovjaga 2016-10-15 10:11:51 UTC
Not reproduced with my dbgutil build. Hunspell is installed and I copied en-US and en-GB dicts to the folder.

Arch Linux 64-bit, KDE Plasma 5
Build ID: 810e664de088721b6452016d83fb3ef3e6ca5eb1
CPU Threads: 8; OS Version: Linux 4.7; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on October 15th 2016
Comment 3 Aron Budea 2017-01-19 04:33:28 UTC
Not reproduced with a few weeks old self-built dbgutil build (87fce022c65c1d2aed1ca59967137d77d936043c, 16-12-29). Setting WFM.

Probably got fixed by hunspell update:
2016-12-14	update to latest hunspell 1-5 release