This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Using windows 7 64-bit with a 64-bit jvm 1. pin netbeans to the taskbar 2. Start netbeans from said taskbar We expect the icon to "light up" since the program is active. Instead another slot in the task bar is created for netbeans. This issue cannot be reproduced using windows 7 64-bit with a 32-bit jvm.
This occurs in 6.8 RC1 and RC2. This does not occur with 6.7.1
Probably caused by the fact that if 32bit JVM is used NB executable and JVM runs in the same process. If 64bit JVM is used separate process is started for JVM. The behavior should be same in 6.7.
(In reply to comment #2) > Probably caused by the fact that if 32bit JVM is used NB executable and JVM > runs in the same process. If 64bit JVM is used separate process is started for > JVM. The behavior should be same in 6.7. And yet it isn't.
(In reply to comment #2) > Probably caused by the fact that if 32bit JVM is used NB executable and JVM > runs in the same process. If 64bit JVM is used separate process is started for > JVM. The behavior should be same in 6.7. Nope. It is caused by the fact that the netbeans.exe is a 32bit application. It tries to load the 64bit jvm inside it's own process which of course fails, so it reverts back to starting the jvm as another process. It is pretty easy to fix: add a 64bit netbeans64.exe file as loader for 64bit jvms.
This is still a problem with 6.9.
We could generate netbeans64.exe, nbexec64.dll and installer could use them on 64bit windows.
There is quick temporaray solution for that issue - you must specify additional command-line option for the netbeans.exe like this: "C:\Program Files\NetBeans\bin\netbeans.exe" --jdkhome "C:\Program Files (x86)\Java\jdk" This will force netbeans launcher to use 32-bit JDK and, in result, it will stay under pinned icon. So you must: - pin netbeans.exe to the taskbar - right-click that pinned icon and in the context menu right-click on "NetBeans IDE 6.x" - from that 2nd menu select "Properties" - in the window that will popup find "Target:" field and change it's content to "C:\Program Files\NetBeans\bin\netbeans.exe" --jdkhome "C:\Program Files (x86)\Java\jdk" - click "OK" to close window - now NetBeans will work under pinned icon but will use 32-bit Java as default (you can still run your projects under 64-bit Java but you must add and select new platform under Java Platform Manager that's found under Tools->Java Platforms menu)
*** Bug 198262 has been marked as a duplicate of this bug. ***
This is still a problem in NB 7. IMHO, best option would be to have a compiled "netbeans64.exe" for windows x64 and have it deployed ini the /bin directory, together with "netbeans.exe" (win x86) and "netbeans[.sh]" (GNU).
Won't be fixed for 7.0.1.
"Won't be fixed for 7.0.1." wait, what? Why not? This is a very obvious and annoying bug for people with Windows 7 64-bit and it makes Netbeans look very unprofessional when it is the one application that fails to integrate with the taskbar. Suggestion in comment #7 does not work for me.
*** Bug 189577 has been marked as a duplicate of this bug. ***
Producing 64-bit launcher is targeted for 7.2.
Assigned to new owner.
Integrated in trunk - core-main/rev/34fef02e9b05. Build for verification will be available in a few days at http://bits.netbeans.org/download/trunk/nightly/latest/
Works for me on Win 7 x64 with Java 64-bit as expected with a latest 7.2 dev build. Reporters, can you verify and confirm as well? Thanks.
After installing Netbeans dev and Java 64bit it works for me now. OS: Windows 7 64-bit Version: NetBeans IDE Dev (Build 201203190400) Java: 1.7.0_03; Java HotSpot(TM) 64-Bit Server VM 22.1-b02
This issue was fixed, but seems to be happening again for me on Windows 10 with NetBeans 8.1 (I had previous versions of NetBeans installed, but have un-installed them: the pinned taskbar icon is for the latest version, and works fine in opening the application, which then creates a duplicate taskbar icon). Naturally I want to use the 64-bit version of Java wherever I am required to use Java, though I am developing for PHP.
(In reply to BlameFate from comment #18) > This issue was fixed, but seems to be happening again for me on Windows 10 > with NetBeans 8.1 (I had previous versions of NetBeans installed, but have > un-installed them: the pinned taskbar icon is for the latest version, and > works fine in opening the application, which then creates a duplicate > taskbar icon). Naturally I want to use the 64-bit version of Java wherever I > am required to use Java, though I am developing for PHP. Could you please attach the launcher log - run the IDE with switch --trace <log file name>
Created attachment 157980 [details] NetBeans startup log file as requested.
This bug also affects Nightly Build 2016-Jan-06. I presume it's still affecting the nightly development builds.
Is your issue still actual? Usually, when such thing occurs it's caused because wrong version of launcher is called. Could you check if you are calling the correct launcher? If the IDE uses 64-bit Java - use netbeans64.exe, if 32-bit Java - netbeans.exe. For me it works...
If the issue still persist for you, please create the new issue, because the origin of the issue may be quite different. Thanks
@LiborFishmeistr: Thanks for your advice! I have now MANUALLY resolved this issue, on my machine! Please explain: why is it not possible for NetBeans to detect which version is installed/ running, and install the correct shortcut icons accordingly, in: "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\NetBeans"? Why would that be such a hard change to put in place, which would after all, resolve this issue for all of us, without any of us having to edit shortcut properties manually in the future??? And why should I duplicate this issue, instead of someone actually resolving the underlying issue, which now looks very simple indeed to resolve?
p.s. My shortcut target now looks like this: "C:\Program Files\NetBeans Dev 201603070002\bin\netbeans64.exe" -J-Dnb.php7=true
(In reply to BlameFate from comment #24) > And why should I duplicate this issue, instead of someone actually resolving > the underlying issue, which now looks very simple indeed to resolve? Because the original cause was quite different. Your issue may be caused by nested JRE... Thanks
⇒ ONE issue, MULTIPLE causes. The original title and description of the issue still apply perfectly well, to the issue I am experiencing! If you want to handle this another way, please duplicate this issue yourself (leading to confusion over duplicated issue titles, no doubt; but if you insist!) Please copy me in on the new issue number, in this case.