Hello ONLYOFFICE Support Team,
I am experiencing a recurring crash when using the Antidote 12 proofreading plugin with ONLYOFFICE Desktop Editors on Windows 11.
The issue occurs while applying corrections. After several successful corrections, the connection between Antidote and ONLYOFFICE is lost. Antidote then indicates that the ONLYOFFICE document is closed, preventing me from continuing the correction session.
1. Software configuration
-
Operating system: Windows 11, 64-bit
-
ONLYOFFICE Desktop Editors Community: 9.4.0.129 (x64 EXE)
-
Antidote: version 12
-
Antidote integration plugin: installed through ONLYOFFICE
-
Antidote Connectix: installed and operational
-
Original document: DOCX, approximately 40 pages, 49 KB
2. Problem description
When I launch Antidote from ONLYOFFICE, the selected text is correctly transferred to the Antidote corrector.
Antidote opens normally and displays the proposed corrections.
I can apply several corrections successfully, and the changes are reflected in the ONLYOFFICE document.
However, after a variable number of corrections, a crash occurs.
At that point, Antidote reports that the ONLYOFFICE document is closed, and the synchronization link is lost.
The crash does not always occur on the same paragraph.
3. Tests already performed
Test A — Antidote standalone
Antidote works correctly when used independently of ONLYOFFICE.
Result: successful.
Test B — New document with a few sentences
A new document was created in ONLYOFFICE and corrected using Antidote.
Some sessions crashed, while others completed successfully.
Result: intermittent failure.
Test C — Reinstalling the Antidote plugin
The Antidote plugin was removed and reinstalled.
Result: the problem persisted.
Test D — Resetting the ONLYOFFICE cache
The cache folder was renamed, allowing ONLYOFFICE to recreate it.
Result: the problem persisted.
Test E — Small document with 5 to 10 corrections
All corrections were completed. Antidote closed normally, and the document was saved, closed and reopened successfully.
Result: successful.
Test F — First page of the original 40-page document
Only the first page was selected for correction.
Several corrections were applied successfully, but a crash occurred while correcting the last paragraph of the selection.
Result: failure.
Test G — Individual paragraphs
The last paragraph of the original document was corrected successfully.
The preceding paragraph was also corrected successfully.
A subsequent attempt to correct another paragraph near the beginning of the document caused the connection to fail again.
Result: intermittent failure.
Test H — Antidote open without corrections
Antidote remains open normally when no correction is applied.
Result: successful.
4. Windows Event Viewer crash details
Windows Application Event Log:
-
Event source: Application Error
-
Event ID: 1000
-
Date: October 11, 2026, 13:27:01 (local time)
-
Faulting application: editors_helper.exe
-
Application version: 9.4.0.129
-
Faulting module: libcef.dll
-
Module version: 109.1.18.0
-
Exception code: 0x80000003
-
Fault offset: 0x000000000694f46b
-
Faulting application path: C:\Program Files\ONLYOFFICE\DesktopEditors\editors_helper.exe
-
Faulting module path: C:\Program Files\ONLYOFFICE\DesktopEditors\libcef.dll
-
Windows report ID: a8047697-55df-434a-a655-c46d3a1ebbd0
The same exception code, module and fault offset were also observed in an earlier crash report.
5. Developer console observations
I launched ONLYOFFICE with the following parameter:
--ascdesktop-support-debug-info
The developer console initially displayed messages including:
-
api.js:580 some errors occurred in the desktop app while document opening -
Contents.json: Failed to load resource: net::ERR_FILE_NOT_FOUND -
Blocked script execution ... frame is sandboxed -
DevTools failed to load source map
After clearing the console, I launched Antidote and started applying corrections.
No additional messages appeared in the editor console before the Antidote connection was lost. I could not return to that console after the failure.
6. Expected behavior
Antidote should allow me to correct selected text or an entire document without losing the connection to ONLYOFFICE.
All accepted corrections should remain synchronized with the document.
7. Questions for the development team
-
Is this a known issue involving Antidote 12, ONLYOFFICE 9.4 and libcef.dll?
-
Could repeated correction synchronization operations trigger a Chromium Embedded Framework assertion or breakpoint?
-
Are there compatibility limitations or known issues involving the Antidote plugin and ONLYOFFICE Desktop Editors 9.4.0.129?
-
Which logs or crash dumps would be most useful for identifying the cause?
-
Is there a recommended workaround or a planned fix?
I can provide additional diagnostic information or perform specific reproduction tests if required.
Thank you for your assistance.