| BPMN2 Property Page Redraw Loop [message #1803691] |
Wed, 06 March 2019 20:41  |
 Michael Wellman
Messages: 1
Registered: March 2019 |
Junior Member |
|
|
For whatever reason, the BPMN2 Property Page Redraw process gets called far too often. It gets called when there is no redraw required, and when there are redraws required, it gets called repeatedly, to the point that it significantly slows down Eclipse for several minutes (or hours). I do not know enough about the Eclipse or BPMN2 source code to know where the fault lies. If it's an event respondant, then perhaps the event is being produced by Eclipse too often, or perhaps it's responding to the wrong event and thus being called more often than it should be. Complicating matters, the redraw problem doesn't happen consistently, but seems to be more likely the longer Eclipse continues to run (typically, I need to restart my computer after around 4-5 hours of continuous Eclipse usage, or the BPMN2 Property Page Redraw process is continually running and sleeping and slowing everything, including typing, to a crawl).
Would it perhaps be possible to simply update the page state (in a Redux-esque sort of architecture), then wait for the master update to run and add the new data to the view, rather than calling a separate component update process that's apparently more process intensive than it should be? This would limit the number of updates necessary, which should vastly improve the user experience for BPMN2. I realize that, for many developers, this is probably a dead project at this point (7 years is ancient to some people) but some of us still use it. I mean... it's a huge step up from when I was a military contractor maintaining 1980s and 90s era systems.
|
|
|
|
Powered by
FUDForum. Page generated in 0.02558 seconds
] 
Search
Help
Register
Login
Home
