Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Enabling Node.js in PProPanel sample crashes the debugger

See original GitHub issue

Problem: The extension refreshes by itself after resume the script execution

To reproduce the bug, first you need to enable Node.js in PProPanel:

  • Change ExtensionManifest Version from 4.0 to 6.0
  • Move CEFCommandLine from DispatchInfo to the Resources tag


<?xml version="1.0" encoding="UTF-8"?>
<ExtensionManifest Version="6.0" ExtensionBundleId="com.adobe.PProPanel" ExtensionBundleVersion="11.1"
ExtensionBundleName="Premiere Pro sample panel"
		<Extension Id="com.adobe.PProPanel" Version="10.3.0" />
			<Host Name="PPRO" Version="9.0" />
			<Locale Code="All" />
			<RequiredRuntime Name="CSXS" Version="6.0" />

		<Extension Id="com.adobe.PProPanel">
			<DispatchInfo >
					<Menu>PProPanel (SDK sample panel)</Menu>

Steps to reproduce the bug:

  • Add a breakpoint in the Chrome debugger
  • Trigger an action to execute the code with the breakpoint
  • The script execution is stopped
  • Resume the execution (F8) or Step over/into the next function (F10/F11)
  • The extension refreshes by itself, preventing the correct debugging for the extension

Enviroment to reproduce the bug:

  • CEP 8.x (Premiere Pro 2018)
  • Windows 10
  • Extension with Node.js enabled
  • Breakpoint in any JavaScript code


  • I couldn’t reproduce it on Mac

Breakpoint ppropanel-debugger-windows

After resume the execution, the extension reloads automatically ppropanel-debugger-windows-2

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:2
  • Comments:9 (3 by maintainers)

github_iconTop GitHub Comments

bbb999commented, Apr 18, 2018

The problem is in CEP.

You may be right. This problem report is specific to PProPanel.

No PPro panel developer has reported problems debugging Node.js.

If the problem is reproducible in CEP HTML Test Panel, we can have the CEP team investigate further.

nbabanovcommented, Apr 18, 2018

@bbb999 NodeJS works on any project. The problem with it is, that it breaks the CEP Chrome remote debugging. It is not related exclusively to any sample. The problem is in CEP.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Debugging - Getting Started - Node.js
This guide will help you get started debugging your Node.js apps and scripts. ... See the section on 'Enabling remote debugging scenarios' on...
Read more >
How to Debug Node.js Segmentation Faults - HTTP Toolkit
You'll know this happens because node will hard crash, exiting silently without any kind of real stack trace, perhaps printing just segmentation fault...
Read more >
How to Debug Node.js Code Using Multiple Tools - Kinsta
This tutorial demonstrates various tools to debug node applications and find their root causes. Dig in and learn from the ground up.
Read more >
Taming the dragon: using llnode to debug your Node.js ...
This is possible through llnode : a LLDB plugin which enables us to inspect Node.js core dumps. With llnode , we can inspect...
Read more >
How to Debug a Node.js Application: Tips, Tricks and Tools
If you're lucky, your code will crash with an obvious error message. ... NODE_DEBUG enables debugging messages using the Node.js ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found