I hope we can triage this problem successfully together, in the log everything seems to be normal to me though/
does this happen with previous versions of KNIME AP, or just with the one you just downloaded? Can you please try with the latest nightly build? https://www.knime.com/form/nightly-build
I already tested the preview (nightly from 25.11) which was fine.
The lastest nightly build is also fine.
I have 3.6.1 running without problems.
For curiosity, I downloaded 3.6.1 and updated it to 3.6.2. Even that works…
To be sure, I tried to reproduce the problem - and it’s gone.
I cannot explain if there is anything different to what I did yesterday. But I repeated the installation of 3.6.2 twice with the same result of half screen grey yesterday. The installer did not change overnight, I guess.
I am happy for you that the problem is gone, too bad we could not identify it’s cause though.
I have recently installed KNIME and i am having a similar issue. The first time i logged in it looked fine and when i tried to move it around i now have half a grey screen. I have tried the following without success:
- starting a new workspace
- loading another workspace
- clicked reset perspective
I am on a Windows 10 (Version 10.0.12134 Build 17134) and on Version 3.7.0
did you try downloading a fresh version of KNIME Analytics Platform (e.g. the archive, not the installer) and try with that? Also sometimes a restart of your computer might help. Please report back if the problem persists.
I have tried downloading it from the archive and restarting my laptop but hasn’t worked. See below screenshot i get on opening KNIME. Any help would be greatly appreciated!
I notice from your screenshot that your application window is maximized; if you click on the maximize button again and then drag-resize the application window - does it in anyway affect the size of the gray area? … and if you reset the perspective while the application window is not maximized?
Thanks for looking at this. I have tried both these and still doesn’t seem to work, screenshot below is after i reset the perspective as you suggested
How strange - if you maximize the workflow editor pane - by either double clicking on the tab for your workflow, or clicking the maximize square in that editor pane - does it maximize to half-width of the application window or full-width?
When i maximise it it only goes to half width, see screenshot
Well that is just cuckoo-banana.
If i provided you with a patch jar so that we could dump some diagnostic logging, would you feel technically comfortable copying it in to your KNIME install (following instructions similar to this: Workflow freeze & graphics problems with KNIME 3.7 )?
Hi quaeler, yes i can give it a go. Thanks for helping out!
Ok, give me a day or two to figure out what I want to ask your KAP, code it, and make a jar. Presuming you’re in Europe given when you post, I’ll likely have a jar by your Friday morning.
Yes i am, speak later this week
There is a patch jar here: http://theori.st/take_away/knime/11185/editor.jar (or http://theori.st/take_away/knime/11185/editor.jar.zip if you have supervising software that doesn’t like JAR files to be downloaded). It also includes the fixes dealing with freezes under Windows so that it won’t be an issue of concern when troubleshooting this issue.
After downloading the jar, in KNIME make a new workspace and switch to that workspace. Quit KNIME, then:
on Windows using Explorer, find your
on Mac right-click / ctrl-click on the KNIME 3.7.0.app and choose ‘Show Package Contents’. Navigate to the
in this directory, rename the existing
editor_jar.bak) so that you still have it around if you want to revert. Then copy the downloaded
editor.jar into this directory and run KNIME.
Once KNIME is finished launching, make a new workflow (this should be the first workflow in your new workspace.) To dump diagnostics one time, click the “Show Node Ids” button in the toolbar (the one with an eye and “#ID” below it) - it is also available via the Node menu.
The console will print a message telling you where on your filesystem you can find the file with the dump, like:
WARN ShowNodeIdsAction Will dump diagnostics...
WARN ShowNodeIdsAction The diagnostics log has been written to [/some/file/path] please rename it appropriately before shipping it off - thanks.
The information collected is mostly anonymous; there will potentially be a file path listed to a jar - if you would like to redact this, please preserve the path atoms (e.g
Please collect diagnostics for the following situations and rename each generated file to reflect these (perhaps using their numbers.)
- maximized application window, normal editor
- maximized application window, maximized editor
- regular window, normal editor
- regular window, maximized editor
Lastly, please put these 4 diagnostic files (redacted as you see fit,) along with the
knime.log from your new workspace, into a ZIP file and attach it to your next reply in this thread.
Thank you for your help - hopefully this helps us figure out what is going wrong, or at least the next question to ask.
Hi qualer, see attached diagnostics jar. Please let me know if you need anything else
knime diagnostics.zip (10.7 KB)
Thanks for the ZIP file; in it, you included a log configuration file (
log4j3.xml) but I was hoping for you to include the
knime.log file that is in the
.metadata/knime directory where your new workspace was created. Could you include that as well?
Also, just to verify - these diagnostic dumps were created after just launching KNIME and making a new workflow - nothing else was done in KNIME (aside from resizing the windows as described?)
I am a new MACOs user and i have the same problem with the latest version.
The bug is not only annoying, it is a show-stopper.
it’s been almost a year and it is not yet solved.
Is someone looking at the problem?
We’ve looked at the problem but are unable to reproduce it (which is not to say that we believe it doesn’t happen for people.) Unfortunately, without a way to reproduce it, we have no way to debug (and fix) it; the diagnostics dump of the instrumented display which matteast92 provided was, again unfortunately, not illuminating.
For curiosity, if you have time, could you download Eclipse IDE for Java Developers version 4.7 from here ( https://www.eclipse.org/downloads/packages/release/oxygen/3a ) and run it on your desktop to see if you also see this half screen issue.
Also, are you running the application on the primary monitor, or a second monitor? If a second monitor, is there a DPI difference between the two? (For example, the second monitor is not a retina monitor and your primary monitor is running in retina mode…)
can you try with a different workspace? In my experience this can fix this bug for some people.
Just click File -> Switch Workspace and select a new folder.