-
1. Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
maxandersen Apr 1, 2011 12:51 AM (in response to bcn)1 of 1 people found this helpfulYes, run with a 32-bit JavaVM then it willl be able to load the xulrunner UI even on Windows 64.
-
2. Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
bcn Apr 2, 2011 11:20 AM (in response to maxandersen)Yes, but then I am much limited on the memory I can give to Eclipse. Well, I guess there is no other way.
Are there at least plans to come up with a 64 bit-version? 64 bit is already very common.
Thanks,
Ulrich
-
3. Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
maxandersen Apr 4, 2011 7:22 AM (in response to bcn)hmm - eclipse should not be requiring that much memory that you need a 64bit memory space to let it run!!
If your eclipse is using more than 2 GB of memory there is something very wrong. Heck, even more than 1 GB is bad.
About 64 bit edition, then the visual editor depends on xulrununer which unfortunately is not available in a stable 64 bit version.
We have thus made it so you can run 99% of JBooss Tools with 64 bit but when you use the visual page editor it will show an error;
anything else should just work.
-
4. Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
mareshkau Apr 4, 2011 7:43 AM (in response to maxandersen)Hi,
Under windows x64+javax32 maximum amount of memory is 667 mb for eclipse. See https://issues.jboss.org/browse/JBIDE-2720
-
5. Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
bcn Apr 5, 2011 6:53 AM (in response to mareshkau)Thanks for the replies.
Yes it would be really nice if all this would be fixed soon. I have voted for the feature request.
Regards,
Ulrich
-
6. Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
maxandersen Apr 5, 2011 12:01 PM (in response to mareshkau)Maxim, where do you get 667M from ?
My 32 bit vm on Windows 7 doesn't stop before I go beyond 1600MB...i.e. 1.6GB which is already rather big.
-
7. Re: Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
prefabsoft May 27, 2011 11:03 AM (in response to maxandersen)"If your eclipse is using more than 2 GB of memory there is something very wrong. Heck, even more than 1 GB is bad."
And 640kb should be enough for anyone?
With all due respect, since eclipse is pluggable that statement makes no sense imho. If you use Springsource Toolsuite for Java development. Plug Aptana3 into it for HTML5+js development. Add some other smaller plugins and JBoss Tools...you will get there. Unfortunately Adobe's Flash builder is also restricted to 32 bit otherwise I could plug it in too. (still have 1 flex project running)
I've already seen my eclipse take up 2 to 3gb at times, still running nicely. (my laptop has 16gb of ram and I notice Eclipse running smoother with higher mem settings e.g.:
--launcher.XXMaxPermSize
1024M
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Dosgi.requiredJavaVersion=1.5
-Xms320m
-Xmx6144m
-XX:MaxPermSize=2048m
For the record, I'm not saying I use all the junk I've got installed into Eclipse but I like to have all tools in 1 app, and the time to configure a less bloated Eclipse isn't worth it. I prefer the "live and let die" minded Eclipse config appoach.
Anyway, I would also love to see a 64 bit version of JBoss Tools since it's supposed one of (or the) best for JSF2 development...and I guess I'm not the only developer who thinks this way.
Best wishes,
Jochen
-
8. Re: Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
maxandersen May 27, 2011 11:19 AM (in response to prefabsoft)Jochen Szostek wrote:
"If your eclipse is using more than 2 GB of memory there is something very wrong. Heck, even more than 1 GB is bad."
And 640kb should be enough for anyone?
With all due respect, since eclipse is pluggable that statement makes no sense imho. If you use Springsource Toolsuite for Java development. Plug Aptana3 into it for HTML5+js development. Add some other smaller plugins and JBoss Tools...you will get there. Unfortunately Adobe's Flash builder is also restricted to 32 bit otherwise I could plug it in too. (still have 1 flex project running)
My comment was in context of Eclipse + JBoss Tools; just using that should never make you go that high unless you are doing something very memory heavy.
We should not accept that just installing plugins and not using them takes up large amounts of memory - that needs to be found and fixed.
I
've already seen my eclipse take up 2 to 3gb at times, still running nicely. (my laptop has 16gb of ram and I notice Eclipse running smoother with higher mem settings e.g.:
--launcher.XXMaxPermSize
1024M
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Dosgi.requiredJavaVersion=1.5
-Xms320m
-Xmx6144m
-XX:MaxPermSize=2048m
For the record, I'm not saying I use all the junk I've got installed into Eclipse but I like to have all tools in 1 app, and the time to configure a less bloated Eclipse isn't worth it. I prefer the "live and let die" minded Eclipse config appoach.
I understand that, and for use adding extra MaxPermSize is a good way to improve eclipse general performance (but that shouldn't make us and other plugin writers sloppy thus I would like to find the leaks if they exist and remove them - that would allow you to install even more
You should be able to run it with 64 bit - it just won't load the visual page editor.Anyway, I would also love to see a 64 bit version of JBoss Tools since it's supposed one of (or the) best for JSF2 development...and I guess I'm not the only developer who thinks this way.
Is it the visual page editor you want ? Then for now it will only run with 32-bit on windows unfortunately.
Jochen
-
9. Re: Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
adelara Aug 11, 2011 9:47 PM (in response to maxandersen)It's just that 64-bits Eclipse runs much faster than the 32-bits on a Win7-64 for example. Like UJ already stated, "64 bit is already very common.", and I add that 64-bits must be the platform of choice for development due to the ton-load of tools we all use on a day-to-day basis.
-
10. Re: Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
maxandersen Aug 12, 2011 11:39 AM (in response to adelara)Yes, I'm aware of that but there is no 64-bit version of xulrunner that will work with 64-bit SWT at the current time of writing.
Thus you have two options on Windows:
Run with 32-bit and have all the visual page editor features.
Run with 64-bit and don't have the visual part of the page editor working - all the code completion,navigation etc. and in the source tab will continue to work.
I wish I had the magic wand to fix it but not something we've found a solution for.
-
11. Re: Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
adelara Aug 19, 2011 12:07 PM (in response to maxandersen)although not vital for me as I can live without the visual part, apparently they sneaked in 64-bits builds...
http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/6.0b5/runtimes/
-
12. Re: Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
henk53 Aug 19, 2011 6:14 PM (in response to adelara)Alex DeLara wrote:
although not vital for me as I can live without the visual part, apparently they sneaked in 64-bits builds...
http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/6.0b5/runtimes/
Link seems to be dead.
http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/6.0/runtimes/ doesn't lists any 64 bits version. I wonder btw if it's even possible to create a 64 bits version of xulrunner for Windows and OS X without doing some MAJOR rewrite of the source code.
-
13. Re: Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
adelara Aug 23, 2011 12:11 PM (in response to henk53)No kidding !!!!! I looked twice and now it's gone...
Apparently someone is toying with renaming and moving stuff around..... how nice is that ?
Did a quick navigation and came up with the link again... just remove "b5"
http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/6.0/runtimes/
-
14. Re: Could not open the Visual Page Editor: Current platform 'win32.win32.x86_64' is not supported.
yradtsevich Sep 6, 2011 3:25 PM (in response to adelara)I have never seen win-x86_64 builds of XULRunner 6. But it is possible that they are existing, since FireFox nighly builds have win-x86_64 version now http://nightly.mozilla.org/.
The problem is that the lastest version of XULRunner supported by Eclipse is 1.9.x. So even if we find these XULRunner 6 builds, it unlikely helps us.