Crash creating new workflow

[Rothstein]

Hi guys. Running KNIME version 3.7.1. Every time I create a new workflow KNIME will crash. After restarting KNIME the workflow is there and I can work in it without any problem. Any clues what is causing this? Underneath is what the log says when creating a new workflow.

O/S: Windows 10.

Log:

2019-04-02 09:00:27,503 : DEBUG : ModalContext : LocalWorkspaceContentProvider : : : Refreshing “/”
2019-04-02 09:00:27,537 : DEBUG : ModalContext : LocalWorkspaceFileStore : : : Refreshed resource R/
2019-04-02 09:00:27,542 : DEBUG : ModalContext : LocalWorkspaceContentProvider : : : Refreshing “/test03”
2019-04-02 09:00:27,543 : DEBUG : ModalContext : LocalWorkspaceFileStore : : : Refreshed resource P/test03
2019-04-02 09:00:27,826 : DEBUG : main : WorkflowEditor : : : Creating WorkflowEditor…
2019-04-02 09:00:27,842 : DEBUG : main : WorkflowEditor : : : creating editor actions…
2019-04-02 09:00:27,974 : DEBUG : main : WorkflowEditor : : : Initializing editor UI…
2019-04-02 09:00:27,974 : DEBUG : main : WorkflowEditor : : : Opening workflow Editor on workflow.knime
2019-04-02 09:00:27,975 : DEBUG : main : WorkflowEditor : : : Setting input into editor…
2019-04-02 09:00:27,978 : DEBUG : main : WorkflowEditor : : : Resource File’s project: file:/C:/Users/xxx/knime-workspace/test03/
2019-04-02 09:00:28,102 : INFO : ModalContext : LoadWorkflowRunnable : : : New workflow created.
2019-04-02 09:00:28,106 : DEBUG : ModalContext : NodeContainer : : : Workflow Manager 2 has new state: EXECUTED
2019-04-02 09:00:28,107 : DEBUG : ModalContext : WorkflowManager : : : Created subworkflow 2
2019-04-02 09:00:28,107 : DEBUG : ModalContext : WorkflowManager : : : Added new subworkflow 2
2019-04-02 09:00:28,107 : DEBUG : ModalContext : NodeContainer : : : ROOT has new state: IDLE
2019-04-02 09:00:28,107 : DEBUG : ModalContext : WorkflowManager : : : Created project 2
2019-04-02 09:00:28,108 : DEBUG : main : WorkflowEditor : : : Saving workflow Workflow Manager 2
2019-04-02 09:00:28,228 : DEBUG : ModalContext : LocalWorkspaceContentProvider : : : Refreshing “/test03”
2019-04-02 09:00:28,281 : DEBUG : main : SVGExporter : : : Not saving SVG to workflow (viewer is null)
2019-04-02 09:00:28,327 : DEBUG : main : ProjectWorkflowMap : : : Adding “file:/C:/Users/xxx/knime-workspace/test03/” to project map (1 in total)
2019-04-02 09:00:28,333 : DEBUG : main : ProjectWorkflowMap : : : registering org.knime.workbench.editor2.WorkflowEditor@3f471e59 to file:/C:/Users/xxx/knime-workspace/test03/. 1 registered clients now.

[ipazin]

Hi there!

Welcome to KNIME community!

Sry for inconvenience. Just to understand better how do you create new workflow? Copy-pasting workflow reproduces some issues or not?

Br,
Ivan

[Rothstein]

What I do is as follow:

1. Start KNIME
2. File -> New
3. Workflow wizard is executed
4. Select “new KNIME Workflow” on top (just an empty template)
5. Name the workflow and keep the “Destination of the workflow” default (LOCAL:/)
6. Select “Finish”

Followed by Windows “KNIME stopped working” dialog message. When re-starting KNIME the flow exists and can be opened.

When I copy and paste an existing workflow in the KNIME explorer, this is executed accordingly without any issues.

[ipazin]

Hi!

I see. I have checked and my log when creating a new workflow looks exactly the same. In folder .metadata there is also log file .log. Maybe there is more information

Is this behavior introduced with some KNIME update or is like this from beginning?

Br,
Ivan

[Rothstein]

The behavior is there since the installation of KNIME (version 3.7.1).

Started KNIME clean and tried to create a workflow. It seems to crash after the workflow is created. This is because I see the workflow appearing as a tab just before it is crashing.

The following appears in the .log :

!SESSION 2019-04-02 13:58:38.924 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_152
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86_64

!ENTRY org.eclipse.ui 2 0 2019-04-02 13:59:01.737
!MESSAGE Warnings while parsing the key bindings from the ‘org.eclipse.ui.commands’ and ‘org.eclipse.ui.bindings’ extension point
!SUBENTRY 1 org.eclipse.ui 2 0 2019-04-02 13:59:01.737
!MESSAGE Cannot bind to an undefined command: plug-in=‘org.knime.workbench.editor’, id=‘knime.commands.editor.gridSettings’

After restarting KNIME again the following appears in the log:

!SESSION 2019-04-02 14:02:35.842 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_152
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86_64

!ENTRY org.eclipse.core.resources 2 10035 2019-04-02 14:02:56.123
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.eclipse.ui 2 0 2019-04-02 14:02:57.092
!MESSAGE Warnings while parsing the key bindings from the ‘org.eclipse.ui.commands’ and ‘org.eclipse.ui.bindings’ extension point
!SUBENTRY 1 org.eclipse.ui 2 0 2019-04-02 14:02:57.092
!MESSAGE Cannot bind to an undefined command: plug-in=‘org.knime.workbench.editor’, id=‘knime.commands.editor.gridSettings’

[ipazin]

Hi!

Not sure what is happening. My log is the same. I would try to uninstall KNIME and install it again. If there is same behavior hope someone else will jump in with some idea

Br,
Ivan

[Rothstein]

Thanks for looking into it! I am restricted in uninstalling and re-installing KNIME by company policies. Hopefully the problem will be solved in the future. At least I have a workaround.

[ipazin]

Ok. I see. Possibly there is some program shutting down KNIME when creating new workflow. Maybe check it with your IT department. If you find out something come back to us please.

You are welcome.

Happy KNIMEing!

Br,
Ivan

[quaeler]

When you say “crash” - do you mean that the application is no longer seen in the task bar at the bottom, or that it enters a state which you need to kill it via Task Manager, or door #3?

[Rothstein]

It crashes with the “KNIME stopped working” standard Windows error. So no killing through task manager.

Update: I am under the impression it has something to do with an external screen / docking station connecting. When I create a new flow on my machine (laptop) without a docking station attached KNIME doesn’t crash. When connected to the docking station it does crash.

[ipazin]

Hi there!

Interesting. Here is a topic where multiple monitors (I guess docking station was included) was causing a issue. Not sure it is connected though.

Send to Tableau Server (Hyper) works with Tableau Online only?

Hi Scott - that setting doesn’t work because Hyper wants the other package. I find something interesting which may be useful for the rest of the community. I have 3 monitors - my laptop (monitor 1) and 2 other monitors (monitors 2 and 3). When the laptop is on the docking station, my main monitor is Monitor number 2. So KNIME starts on Monitor number 2. And then, I move KNIME to monitor 3 (larger monitor) and I work on my workflows there. This is when things get really interesting - when I br…

Br,
Ivan

[Rothstein]

This is quite interesting. I have the impression it has to do with external monitors somehow. I cannot exactly pinpoint it. Because when I disconnected the laptop from the docking station today (KNIME was already running) is crashed again when creating a new workflow on the laptop monitor.

This is what the Windows Event viewer says after crash (Error is given four times) :

Faulting application name: knime.exe, version: 0.0.0.0, time stamp: 0x553e7d2c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000000410c0
Faulting process id: 0x3574
Faulting application start time: 0x01d4eab5e7d3746d
Faulting application path: C:\Program Files\KNIME\knime.exe
Faulting module path: unknown
Report Id: f25bc3c9-3462-4a54-9422-cd824c37d087
Faulting package full name:
Faulting package-relative application ID: