• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
Locked
0

FlashBuilder4 eclipse plugin for Eclipse Helios 64 bit version

New Here ,
Jul 19, 2010 Jul 19, 2010

Copy link to clipboard

Copied

Hello,

I installed FlashBuilder4 trial version which is not a standalone application but rather eclipse plugin, in my latest Eclipse installation which is Eclipse Helios 64 bit version. The installation went on smoothly but after i restarted my Eclipse instance and upon clicking the Flex module from Properties menu it popped up quite a few issues.

I did some research and came to know that Adobe is not supporting 64 bit version of Eclipse.

My question is whether it is a problem or am i missing something. Was anyone able to make the FlashBuilder4 work with Eclipse Helios 64 bit version. If not is there any chance of Adobe releasing the plugin which will work in Eclipse 64 bit. This is rather important for us since we are looking to port our application infrastructure to use 64 bit Eclipse, JVM etc and if Adobe is not supporting that it will become a show stopper for us and we have to fall upon using 2 different IDE(s) as a last resort.

Looking forward to  hear from Adobe people soon with few silver linings!!!!!

Here are my system details:

Windows XP SP2 64 bit professional edition, 8 gb RAM, 2.93 Ghz

I tried to make it work on Eclipse Helios JEE 64 bit version with Adobe FlashBuilder4 trial version.

Here is the stacktrace that i could retrieve from my Eclipse Log file hope this helps:

!ENTRY org.eclipse.osgi 4 0 2010-07-06 00:39:06.330

!MESSAGE An error occurred while automatically activating bundle com.adobe.flexbuilder.project (1075).

!STACK 0

org.osgi.framework.BundleException: Exception in com.adobe.flexbuilder.project.internal.FlexProjectCore.start() of bundle com.adobe.flexbuilder.project.

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(Bundl eContextImpl.java:806)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextI mpl.java:755)

    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java :370)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.ja va:284)

    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:417)

    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java: 265)

    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass (EclipseLazyStarter.java:106)

    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathMa nager.java:453)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(Default ClassLoader.java:216)

    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java: 393)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.ja va:469)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClass Loader.java:107)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

    at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:338)

    at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:2 32)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundl e.java:1197)

    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableEx tension(RegistryStrategyOSGI.java:174)

    at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension( ExtensionRegistry.java:904)

    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtensi on(ConfigurationElement.java:243)

    at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableE xtension(ConfigurationElementHandle.java:55)

    at org.eclipse.core.internal.events.BuildManager.instantiateBuilder(BuildManager.j ava:784)

    at org.eclipse.core.internal.events.BuildManager.initializeBuilder(BuildManager.ja va:737)

    at org.eclipse.core.internal.events.BuildManager.getBuilder(BuildManager.java:482)

    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)

    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)

    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)

    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java: 311)

    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)

    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)

    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)

    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Caused by: java.lang.NoClassDefFoundError: com/adobe/flexbuilder/utils/osnative/NativeControl

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.getUserFlashPlayerTrust Folder(Unknown Source)

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.<init>(Unknown Source)

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.getInstance(Unknown Source)

    at com.adobe.flexbuilder.project.internal.FlexProjectCore.start(Unknown Source)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextI mpl.java:783)

    at java.security.AccessController.doPrivileged(Native Method)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(Bundl eContextImpl.java:774)

    ... 33 more

Caused by: java.lang.ClassNotFoundException: com.adobe.flexbuilder.utils.osnative.NativeControl

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.ja va:506)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClass Loader.java:107)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

    ... 40 more

Root exception:

java.lang.NoClassDefFoundError: com/adobe/flexbuilder/utils/osnative/NativeControl

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.getUserFlashPlayerTrust Folder(Unknown Source)

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.<init>(Unknown Source)

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.getInstance(Unknown Source)

    at com.adobe.flexbuilder.project.internal.FlexProjectCore.start(Unknown Source)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextI mpl.java:783)

    at java.security.AccessController.doPrivileged(Native Method)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(Bundl eContextImpl.java:774)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextI mpl.java:755)

    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java :370)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.ja va:284)

    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:417)

    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java: 265)

    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass (EclipseLazyStarter.java:106)

    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathMa nager.java:453)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(Default ClassLoader.java:216)

    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java: 393)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.ja va:469)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClass Loader.java:107)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

    at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:338)

    at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:2 32)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundl e.java:1197)

    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableEx tension(RegistryStrategyOSGI.java:174)

    at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension( ExtensionRegistry.java:904)

    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtensi on(ConfigurationElement.java:243)

    at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableE xtension(ConfigurationElementHandle.java:55)

    at org.eclipse.core.internal.events.BuildManager.instantiateBuilder(BuildManager.j ava:784)

    at org.eclipse.core.internal.events.BuildManager.initializeBuilder(BuildManager.ja va:737)

    at org.eclipse.core.internal.events.BuildManager.getBuilder(BuildManager.java:482)

    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)

    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)

    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)

    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java: 311)

    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)

    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)

    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)

    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Caused by: java.lang.ClassNotFoundException: com.adobe.flexbuilder.utils.osnative.NativeControl

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.ja va:506)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClass Loader.java:107)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

    ... 40 more

!ENTRY org.eclipse.core.resources 4 2 2010-07-06 00:39:07.611

!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".

!STACK 0

java.lang.NoClassDefFoundError: com/adobe/flexbuilder/project/internal/ApplicationResourceListener$1

    at com.adobe.flexbuilder.project.internal.ApplicationResourceListener.resourceChan ged(Unknown Source)

    at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager. java:291)

    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

    at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager .java:285)

    at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(Notificat ionManager.java:149)

    at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.jav a:327)

    at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1181)

    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:157)

    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)

    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNo tFoundException: An error occurred while automatically activating bundle com.adobe.flexbuilder.project (1075).

    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass (EclipseLazyStarter.java:121)

    at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathMa nager.java:453)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(Default ClassLoader.java:216)

    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java: 393)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.ja va:469)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClass Loader.java:107)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

    at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:338)

    at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:2 32)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundl e.java:1197)

    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableEx tension(RegistryStrategyOSGI.java:174)

    at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension( ExtensionRegistry.java:904)

    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtensi on(ConfigurationElement.java:243)

    at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableE xtension(ConfigurationElementHandle.java:55)

    at org.eclipse.core.internal.events.BuildManager.instantiateBuilder(BuildManager.j ava:784)

    at org.eclipse.core.internal.events.BuildManager.initializeBuilder(BuildManager.ja va:737)

    at org.eclipse.core.internal.events.BuildManager.getBuilder(BuildManager.java:482)

    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)

    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)

    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)

    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java: 311)

    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)

    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)

    ... 2 more

Caused by: org.osgi.framework.BundleException: Exception in com.adobe.flexbuilder.project.internal.FlexProjectCore.start() of bundle com.adobe.flexbuilder.project.

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(Bundl eContextImpl.java:806)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextI mpl.java:755)

    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java :370)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.ja va:284)

    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:417)

    at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java: 265)

    at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass (EclipseLazyStarter.java:106)

    ... 27 more

Caused by: java.lang.NoClassDefFoundError: com/adobe/flexbuilder/utils/osnative/NativeControl

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.getUserFlashPlayerTrust Folder(Unknown Source)

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.<init>(Unknown Source)

    at com.adobe.flexbuilder.project.internal.PlayerTrustStore.getInstance(Unknown Source)

    at com.adobe.flexbuilder.project.internal.FlexProjectCore.start(Unknown Source)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextI mpl.java:783)

    at java.security.AccessController.doPrivileged(Native Method)

    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(Bundl eContextImpl.java:774)

    ... 33 more

Caused by: java.lang.ClassNotFoundException: com.adobe.flexbuilder.utils.osnative.NativeControl

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.ja va:506)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)

    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClass Loader.java:107)

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

    ... 40 more

~ Saurabh

TOPICS
Installation and activation

Views

37.0K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
replies 103 Replies 103
New Here ,
Jun 02, 2011 Jun 02, 2011

Copy link to clipboard

Copied

+1 for 64-bit support.

Being able to use a 64-bit JRE in flash builder would be awesome. The 1gb memory limit of 32-bit eclipse/java is annoying. I get out-of-memory errors multiple times a day in FB.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 06, 2011 Jul 06, 2011

Copy link to clipboard

Copied

+100 votes (1 for each developer in our organization)

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 13, 2011 Jul 13, 2011

Copy link to clipboard

Copied

+1 for 64 flash builder!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 05, 2011 Aug 05, 2011

Copy link to clipboard

Copied

+1 for x64 support!

Our team is consistently working with large Flex/Air applications that integrate with many other backend technologies. Unfortunately, the memory limitations of 32 bit eclipse installations are a severely limiting factor when we are trying to work on the entirety of the project within a single workspace. Furthermore, the memory profiler in Flash Builder quickly becomes unusable during large application development because it can't get the resources it needs to run effectively.

Please, Adobe, hear our cries! Give us FlashBuilder x64!

-Matt

P.S. Please also explain the current limitations to delivering one.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Aug 17, 2011 Aug 17, 2011

Copy link to clipboard

Copied

+1 here

I am running into that java heap error. And why haven't you release an IDE in AIR? Do I need to program this too? It would make the application OS independent!

Thomas Pickett

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 17, 2011 Aug 17, 2011

Copy link to clipboard

Copied

Note that the FlashBuilder is an eclipse plugin and eclipse itself is OS independant (as long as SWT is supported on the platform).

On the other hand linux support has been dropped as of AIR 2.6 - so the only supported (desktop) platforms are Windows and Mac OS.

And of course there is an x64 version of eclipse as well as an x64 edition of the JRE available, which is not the case for AIR or flash in general.

I think i will adobt IWantToLikeAdobe's google chrome quote as my signature on this forums:

THE FOLLOWING TECHNOLOGY HAS BECOME UNRESPONSIVE: ADOBE FLEX

Shame on you, Adobe!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 22, 2011 Aug 22, 2011

Copy link to clipboard

Copied

Hi,

First: Eclipse is not OS independant.

Second: Why 64bit? Because it is starting to get hell to compile a enterprise level flex application using a 32bit process which can only use a minimal amount memory. Arrrggg.

I'm working for about 6 months now for my first flex client using flex builder and already fed up with it. Back to HTML/jQuery for me.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Aug 25, 2011 Aug 25, 2011

Copy link to clipboard

Copied

Another vote for 64 bit support. Reason is simple - frequent out-of-memory errors running Helios with both FlashBuilder and server-side related plugins (JEE, STS, etc). The exact errors depend on eclipse.ini setup, from out of permgen, to cannot create another thread, to just fail to compile Flex project with "Unknown Error", each time requiring an Eclipse restart. Adobe puts a lot of marketing emphasis on "user experience", and in general the FlashBuilder UX gets better with each version (at least if we ignore the context sensitive help, which was MUCH better in FlexBuilder). But this frequent out-of-memory situation is an annoyance, not to mention an embarrassment when showing my HTML / JS dev colleagues how we work.

Keep up the good work. Oh, and give us back Eclipse-based help!

Thanks

Tim

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 10, 2011 Sep 10, 2011

Copy link to clipboard

Copied

+1 for 64bit .. It's real pain to do any enterprise sized project - you'r loosing to other IDE's here ... no way anyone can justify all time crashes, deployment problems (which rather goes to WTP) and ultimatelly .. very poor maven support - where I don't really see another way of development then with continuous build based on maven

Our project is some 80 flex and 150+ java/groovy projects. The problem is, that what is being recognized as one of the most important features, is the possibility of continuous development/debugging process for UI to Backend code, within single IDE. That contributes quite a lot to the overall flow of developer's daily tasks. AS3/Flex is great stack for UI building, unfortunatelly, it is really difficult to make a case here if you are unable to integrate it into the factory of sw development. 64bit IDE + compiler would be great step ahead in this competition (but only leveling with the others atm).

Good luck

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Sep 22, 2011 Sep 22, 2011

Copy link to clipboard

Copied

This request has been out for a while - when is Adobe planning on having 64 bit supported?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 22, 2011 Sep 22, 2011

Copy link to clipboard

Copied

Very few developer machines still have less than 4GB Ram and the lack of support from Adobe shows a disinterest in Flex usage in a professional context. Together with the deprecation of Google's map API for flash and other major actors that will follow, I think the safest route is to abandon Flex development all together.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 16, 2011 Oct 16, 2011

Copy link to clipboard

Copied

Andrew,

It looks like this has been going on for at least a year, now. You really do need to provide 64-bit support.

Can you at least release a 64-bit plugin, ASAP?

Have a great week.

Take care,

Darwin

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 18, 2011 Oct 18, 2011

Copy link to clipboard

Copied

+1 vote for the Eclipse 3.7 version with 64-bit support

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Dec 14, 2011 Dec 14, 2011

Copy link to clipboard

Copied

+1 vote for Eclipse 3.7 64bit support (wow... that's one popular demand and it has been here for 17 months...)

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 14, 2011 Dec 14, 2011

Copy link to clipboard

Copied

I'm truely beginning to doubt Adobe's commitment to the community.  This is a travesty!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 14, 2011 Dec 14, 2011

Copy link to clipboard

Copied

At this point with HTML 5 and Adobe pretty much dropping Flash on mobile devices I personally no longer care whether there is a 64 bit version of the IDE as I will no longer be doing any Flash/Flex development. I'm sure it's still important to the rest of the community and I don't want to downplay that but for me it's an issue of too little too late. I'm sure I'm not alone

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 14, 2011 Dec 14, 2011

Copy link to clipboard

Copied

Flash on mobile devices is one thing, enterprise development is another.  Flex has a long future in enterprise development.  Big corporations don't want angry birds or gee-wiz animations.  They want applications that look the same everywhere.  A flex app can be cross compiled to air and run on pads, mobile etc (with some minor tweaks of course).  I'm not sure what the gaming future of flash/actionscript is, but i personally don't care.  Most flex engineers are RIA/enterprise developers.  We have absolutely no use for html other than using it to host a container div for our app.  I intend to learn HTML 5 so I don't deprecate myself, but I think your view is seriously limited if  you think that HTML5 is the second comming of the programming mesiah.  HTML 5 has some very focused usefulness but it is not the end-all-beat-all to flex and never will be.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 14, 2011 Dec 14, 2011

Copy link to clipboard

Copied

Hello,

Without wanting to be pessimistic or finger pointing I have to disagree on the "flex for ever" view. If you ask me the arrival of HTML5 put flex in a EOL state. The absent response by adobe to this thread, Adobe Muse and the arrival of simple tools provided by for example google to transcode flv to html5 says enough.

Not that I think HTML5 is THE future product to focus on. I' m more a believer of a "applications" web but I fear flex is a lost case by then. Sure maintenance will remain for those enterprise applications, but that is it.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 14, 2011 Dec 14, 2011

Copy link to clipboard

Copied

I honistly think nobody needs to vote anymore. 64bit FB will not come at all.

I think this is true because of al the problems i have with flash builder. Flashbuilder imho is unstable.

The hole reason I need 64bit, is so i can allocate more memory (fb keeps crashing with an OutOfMemoryException, this happent in fb3 and is still happening in fb4.6).

I think they have loads of trouble with building flashbuilder as a stable ide anyway, and they focus on that iso 64bit.

My project will move to html5 as soon as the backlog allows it.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 14, 2011 Dec 14, 2011

Copy link to clipboard

Copied

@Majathi, that may be true to some extent as far as flex is concerned, BUT I don't think HTML5 is the technology to replace flex.  HTML5 from flex is a step backwards from a mature (albeit buggy) API to a very new and unproven one.  I also don't see whole enterprise applications being built in HTML5 any time soon.  like I said it's great for angry birds and bouncy balls...  but I'm not sure it is a VIABLE replacement for the FEATURES of flex.  I'm not debating that flex is facing EOL, but it's very far off.  FLASH on the otherhand is AT EOL.  I think that HTML5 will kill flash, but flex does not really have a viable replacement yet.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Feb 08, 2012 Feb 08, 2012

Copy link to clipboard

Copied

I vote for a 64 bit flashbuilder!! 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Mar 19, 2012 Mar 19, 2012

Copy link to clipboard

Copied

All my colleagues and I work with 64bit OS and we experienced performance and stability issues... I vote for 64bit Support!!

Thanks,

Mario

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 10, 2012 Apr 10, 2012

Copy link to clipboard

Copied

Same here. And the problem is Flash Builder crash all the time on Win7 64 bit

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Apr 19, 2012 Apr 19, 2012

Copy link to clipboard

Copied

+1 for 64-bit FB4

We've hit the memory wall and this is becoming a serious issue.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 19, 2012 Apr 19, 2012

Copy link to clipboard

Copied

Hello, everyone!

I created a feature ehancement at Flex JIRA of Adobe.

Now, you can vote officially from the following URL.

https://bugs.adobe.com/jira/browse/FB-33228

thanks

Shigeru Nakagaki

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines