Enabling Node.js in PProPanel sample crashes the debugger
See original GitHub issueProblem: 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
from4.0
to6.0
- Move
CEFCommandLine
fromDispatchInfo
to theResources
tag
manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<ExtensionManifest Version="6.0" ExtensionBundleId="com.adobe.PProPanel" ExtensionBundleVersion="11.1"
ExtensionBundleName="Premiere Pro sample panel"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ExtensionList>
<Extension Id="com.adobe.PProPanel" Version="10.3.0" />
</ExtensionList>
<ExecutionEnvironment>
<HostList>
<Host Name="PPRO" Version="9.0" />
</HostList>
<LocaleList>
<Locale Code="All" />
</LocaleList>
<RequiredRuntimeList>
<RequiredRuntime Name="CSXS" Version="6.0" />
</RequiredRuntimeList>
</ExecutionEnvironment>
<DispatchInfoList>
<Extension Id="com.adobe.PProPanel">
<DispatchInfo >
<Resources>
<MainPath>./index.html</MainPath>
<ScriptPath>./PProPanel.jsx</ScriptPath>
<CEFCommandLine>
<Parameter>--allow-file-access</Parameter>
<Parameter>--allow-file-access-from-files</Parameter>
<Parameter>--enable-nodejs</Parameter>
</CEFCommandLine>
</Resources>
<Lifecycle>
<AutoVisible>true</AutoVisible>
</Lifecycle>
<UI>
<Type>Panel</Type>
<Menu>PProPanel (SDK sample panel)</Menu>
<Geometry>
<Size>
<Height>300</Height>
<Width>180</Width>
</Size>
</Geometry>
</UI>
</DispatchInfo>
</Extension>
</DispatchInfoList>
</ExtensionManifest>
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
Notes:
- I couldn’t reproduce it on Mac
Breakpoint
After resume the execution, the extension reloads automatically
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:9 (3 by maintainers)
Top 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 >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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.
@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.