I just installed Neo4J community for windows10 . The menu can launch Neo4J and shows the small window with 'choose database' and 'stop' and 'start'.
Everything seems ok, i can start, use the db, and stop.
I can restart or stop, as long i don't close this small window.
If i do, i can no more start Neo4J as it is still running in background (seen in task manager ) and never show again this small window.
As a workaround, i kill the app in task manager, then the window re appears on next start .
any idea ?
Even though the window has gone away, the process itself is still running (neo4j-ce.exe). If you open the task manager, look under "Background Processes" and find it there. Select it and then press "End task". You can restart Neo4J after that. I haven't found an answer as to why you have to do this, but it seems to have popped up with the 3.1 version.
When the Neo4j database is stopped by clicking the stop button and the GUI closed by clicking the X in the corner, the Neo4j process continues to run in the background as described by chrisvest Neo4j process still in memory after stopping and closing the window. This is a feature. However, trying to launch the GUI again from the exe or a link to the exe will not work. You will have to locate the small Neo4j icon in the taskbar and click on it. The GUI will reappear. There is no need to kill the Neo4j.ce thread or restart the computer.
Related
Good day,
I'm currently experiencing a weird phenomena, this morning as I open the dbgview application an error message popped out(kernel related), couldn't remember much about the details.
Although the dbgview was showing at the task bar but as I clicked on it, it will jump out to no where.
It was as if I have 2nd monitor and it jump out to other screen.
I checked with 2nd monitor and it was not there..
I tried to install the latest version.
System recovery back to few days before which was still in working condition. But it doesn't help.
Hope someone here could show me some clue.
07/07/2020
I discovered it might not related to debugview this app. As I opened up task bar and select the debugview application and maximize the window size it is showing up. However as long as I click restore button at the right top corner of the app it flew out to the universe again....
Thank you
DbgView remembers its last position, so what likely happened is that you disconnected a monitor while DbgView was running on it, or maybe you accidentally dragged DbgView offscreen, and now it opens in a position that's no longer visible. Try either of the following.
With DbgView running, Alt-TAB to it then press Alt-Space, M (which opens the system menu and selects Move). While the "move" cursor is showing, use the arrow keys to bring the window back onto the active screen.
With DbgView closed, run regedit, navigate to HKCU\Software\Sysinternals\DbgView and delete (or rename) the Settings value, then run DbgView again. Since it no longer finds the old saved position in the registry, it will now open in the default position on the active monitor.
Try this:
start dbgview
hold the left 'Windows key'
while still holding the windo
I have a ruby script that displays it's progress via the cmd and completes in about 10 minutes. In the last few weeks the cmd seems to freeze and after 10 minutes when I click on the cmd window it then completes the script.
I have searched on forums and suggestions include: disable QuickEdit Mode & Insert Mode which I have done but this has not fixed the problem.
The platform is an azure windows server 2016 VM.
Could this problem be due to a recent windows update?
Thanks
If you are using the usual Windows Command Window, Ruby has no way of knowing that you have clicked into the Window, so it is unlikely that it is related to the code. However, Windows does block a command to write to the command window on certain circumstances, and if this happens, Ruby waits on, say, STDOUT.puts, until it is allowed to continue. Of course this applies not only to Ruby, but to any application writing to the command console.
The most typical situation, in which this occurs, is, if you (maybe accidentally) select with the mouse something in the console Window. The script running in the console is blocked. By clicking with the mouse inside the window, the selection is cancelled, and the program continues to run.
I use the RestartAPI to restart my application if I need to reload it. It works fine until I launch any Windows dialog (e.g. Open Dialogue), which ends with Open button being clicked! In this case, if I later choose to restart the new application (after restarting) will not be able to open ANY files. If I click Cancel button the new restarted application will work just fine.
It took me a long time to figure out that the difference between the two restarts is the Open button with some Open Dialog that is completely unrelated to the application restart. Note that I have eliminated the code that gets executed after the Open button is clicked so there's no way that it could be caused by some memory corrupting code that the Open button just initiates.
It is enough to click the Open button once (so I may 5 times click Cancel than once Open and than for example 3 times Cancel) and any attempt to restart the application however "late" will result in the new instance not being able to open any files (not even with std::ifstream).
Some details:
Visual Studio 2010
Windows 7 x64 (but with 32bit XP it is the same)
the dialog is launched in a separate thread
I use Allegro 5.0 for graphics but that should not be related
The dialog is launched by GetOpenFileName function
I don't know about RestartAPI, but you can create temporary batch file which will restart the process without any problems.
I'm trying to debug a VS 2008 command-line application running under Windows XP. The application has been crashing (access violation), and I am catching the crsah in the debuuger. After looking at the call stack, etc., I tell the IDE to "Stop Debugging". The application window remains, but the process does not appear in Task Manager. Nothing happens when I click the "X" in the upper-right corner, though I can minimze / restore the window. The process is normally shut down by pressing Esc. It does not respond to this keypress.
I cannot even get rid of the application window by attempting to reboot XP. The machine will not reboot; it simply ignores my command to do so.
The only way I've been able to get rid of the application window is to do a hard power cycle. Ughh...
Does anybody have any suggestions on how to clean up this lingering application window after the application crashes?
Thanks,
Dave
I'm writing and then debugging a console application in VC++ 2008, it then happens that closing Visual Studio IDE, the console window remain opened, and there is no way to close it!
Also if I try a machine reboot the machine doesn't restart. The only way is turning off the power.
In the process list there are no signs of the console window.
If I try to investigate the console window with tools like Spy++ I found the window but in the "process" tab there is a process ID that doesn't exists, in the "General" tab the "window proc" field says "Unavailable".
How is it possible?
How can I kill those type of windows as there is no processe to kill?
thanks
Most annoying bug ever; get the hotfix.