Why Does Dyalog Crash When Creating an HTMLRenderer Object?

Last updated on: 9 July, 2026

Dyalog typically crashes when creating an HTMLRenderer object if required CEF (Chromium Embedded Framework) files are missing. These files must be present alongside your executable.

Why This Happens

The HTMLRenderer relies on the Chromium Embedded Framework (CEF). If any required CEF components are missing, the renderer cannot initialise and Dyalog may terminate unexpectedly.

Required Files (Dyalog 20.0)

  • htmlrenderer.dll
  • chrome_100_percent.pak
  • chrome_200_percent.pak
  • chrome_elf.dll
  • d3dcompiler_47.dll
  • dxil.dll
  • dxcompiler.dll
  • icudtl.dat
  • libcef.dll
  • libEGL.dll
  • libGLESv2.dll
  • resources.pak
  • v8_context_snapshot.bin
  • vk_swiftshader.dll
  • vk_swiftshader_icd.json
  • vulkan-1.dll

Required Folder

  • locales

Typical Cause

This problem usually appears when creating a custom runtime directory, copying only selected Dyalog files, or omitting supporting HTMLRenderer / CEF files.

How to Fix the Problem

Ensure all required CEF files are present, verify the directory structure matches a working installation, and re-copy files from a clean Dyalog installation if necessary.

Further Reference

See the HTMLRenderer User Guide for a complete file list.

Vince Chan
Still Have an Issue?
If you’ve got a technical query, you might find the answer in our documentation or on our forums. Otherwise, please email us at support@dyalog.com, call +44 1256 830030, or send us a message.

Vince Chan, Customer Support

Get Support