Native spelling implementation crashed
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 58
- Joined: Sat Aug 01, 2009 12:57 am
Native spelling implementation crashed
One of our users received following error.
Code: Select all
The application detected an error that is not automatically handled. It is possible that this error is not critical and the application may continue to work normally but our recommendation is to report the error and restart the application. If the application has become unstable and cannot be closed normally, you can use the Force Quit button from this dialog. Be aware that by doing this you will lose all unsaved changes in the opened documents.
Here are the error details:
[ main ] - The native spelling implementation has crashed in the last editing session.
Now using the Java spelling implementation.
You can re-enable the native spell checker by removing the file:
U:\Users\user.name\AppData\Roaming\com.oxygenxml.author\HunspellCrashGuardSa.txt
and then restarting the program.
Please report this problem to the product support team. Thank you!
-
- Posts: 2879
- Joined: Tue May 17, 2005 4:01 pm
Re: Native spelling implementation crashed
Hello,
Were there multiple instances of Oxygen running when this happened?
If Oxygen didn't crash, then there's nothing to worry about.
This is just a failsafe mechanism that prevents Oxygen from crashing repeatedly in case the Hunspell spell checker has trouble initializing. This failsafe can be triggered accidentally if Oxygen is quit forcefully(end task, your computer is restarted or loses power) or if multiple instances of Oxygen are accidentally started.
Just make sure you delete the file mentioned in the error:
otherwise the native spell-checker(Hunspell) will remain disabled.
Afterwards restart Oxygen and verify the spell-checker state in Options > Preferences, Editor > Spell Check.
The Spell checking engine option should be set to Hunspell(is set by default).
Let us know if you encounter further issues.
Regards,
Adrian
Were there multiple instances of Oxygen running when this happened?
If Oxygen didn't crash, then there's nothing to worry about.
This is just a failsafe mechanism that prevents Oxygen from crashing repeatedly in case the Hunspell spell checker has trouble initializing. This failsafe can be triggered accidentally if Oxygen is quit forcefully(end task, your computer is restarted or loses power) or if multiple instances of Oxygen are accidentally started.
Just make sure you delete the file mentioned in the error:
Code: Select all
U:\Users\user.name\AppData\Roaming\com.oxygenxml.author\HunspellCrashGuardSa.txt
Afterwards restart Oxygen and verify the spell-checker state in Options > Preferences, Editor > Spell Check.
The Spell checking engine option should be set to Hunspell(is set by default).
Let us know if you encounter further issues.
Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service