search

camunda / camunda-modeler

An integrated modeling solution for BPMN, DMN and Forms based on bpmn.io.
https://camunda.com/products/modeler
MIT License
1.47k stars 473 forks source link

Single instance behavior spawns zombie process when using different Modeler versions #3485

Open FO-e-X opened 1 year ago

FO-e-X commented 1 year ago

Describe the bug

Hi,

I downloaded the current version 5.8.0 of the Camunda Standalone Modeler and just started it. I'm still at the landing page without any open diagram. While doing other things, the Modeler is in idle mode. To compare with the older version 4.12 I started this Modeler too, but no new window opens, it just pops the 5.8 on top again. OK, fine, but now I've got 2 tasks called Camunda Modeler. When I close the 5.8 Modeler, the other task still remains and it produces a lot of workload, about 15-19% on my AMD R7 8 core CPU. This is crazy. No open Modeler, a running Modeler taks with a lot of useless workload... The only way to stop it is by killing the task via task manager. When starting 2x V 5.8, this behavior can not be reproduced.

I know, it's a strange usecase and shouldn't occure this often. But maybe it could be checked at start to prevent creating a zombie task.

Regards Frank

Steps to reproduce

  1. start Modeler V 5.8
  2. start Modeler V 4.12
  3. close Modeler V 5.8
  4. look at Windows Task-Manager for the remaining Camunda Modeler task, how it consumes ressources without being usable...

Expected behavior

The start of an older version of the Modeler should not create a zombie task.

Environment

Camunda Modeler system information

Additional context

No response

marstamm commented 1 year ago

Thank you for reporting this bug. I can also reproduce it using newer versions as well, e.g. 5.8.0 and 5.0.0, but not consistently.