been using the gwt plugin in eclipse for about a year, has worked pretty fine.
However, i recently upgraded to OSX lion, and i also upgraded intellij to latest version.
Now, i have a standard gwt project. I have historically been able to start it with the devconsole, change stuff and reload page in firefox. (using firefox5 currently)
But now, i can only start it, but as soon as i reload page, devconsole crashed. Yesterday it just hung, this morning i upgraded to GWT2.4 and now i just get permgen space outofmemory on first reload. I have the memory settings set to 1024m!
If someone could give me pointers it would me much appreciated...
I experienced that same issue after upgrading to Lion. I believe it has something to do with the memory management of OSX, not Eclipse or GWT. It was a source of huge inconvenience to me, and the benefits of the Lion upgrade weren't enough to justify dealing with an impaired capacity for development, so I rolled back to Snow Leopard. That resolved the problem.
I've since tried (unsuccessfully) going back to Lion and using different browser combinations, including Safari and Chrome, but Firefox still seems to be the best choice if you're using Lion- Chrome is exceptionally slow with GWT (oddly), and Webkit in general seems to not support some of the features GWT offers, so Safari's out.
I say go back to Snow Leopard, unless there's something preventing you from doing so. Good luck, and please keep us updated if you figure out a workaround.
Answering my own question since i've found well, not an answer but a workaround.
In intellij, i changed the agent (only using one in development to speed things up) from gecko1_8 to safari, and used chrome.
As i mentioned, the console crashed in firefox on every reload, in Chrome i'm at 30 page reloads/recompiles and not a single console crash!
It also recompiles faster than in FF.
Have no idea why it works so crappy in FF though...
You can fix it - just add -XX:MaxPermSize=384m for jvm.
Related
I'm subscribing to Adobe CC just for FB and Flash Pro. This bug seems undocumented but is hugely annoying. It has not always been this way - it developed over time, and for awhile if I toggled wifi and restarted it would work again. It is definitely not a workspace corruption; I've reinstalled FB, I've tried different workspaces. What happens is that when wifi is on, or as long as the computer is allocated an external IP, Flash Builder 4.7 works. If wifi is off, or if it fails to find a network, FB crashes before it tries to load the workspace.
Interestingly, if I create a wifi network, assigning my own box a 192.168.. address, FB launches. But if I turn off wifi while FB is open, it throws an error when I try to save files, and throws another error when I quit, saying it can't save the workspace. It's beyond me why, but FB is obviously failing read/write in the absence of a non-local IP being allocated to the box.
This happens even with a clean install and no projects or dependencies.
Has anyone encountered this one? FWIW, I'm also running Eclipse Helios and Kepler, as well as Flash Builder 4 on the same box for maintaining older code - plus Flash Pro and the rest of the CC without any problems. What is up with FB 4.7 ?! I wish Adobe had just put out a damn Eclipse plugin instead of this pile of **** I'm paying $50 a month for. To be an IDE that fails whenever I can't get online.
I can't upgrade OS X on this box, but I doubt it would make a difference, since this is a Java error of some kind and FB hasn't been updated since 2013 or so anyway. It used to work. Unless I got infected with a worm that's trying to upload things I write, I don't see a reason it stopped unless some perms or base code got corrupted. Any insight would be welcome.
This turns out to be a problem with localhost domain resolution on OS X. A workaround can be found here:
InetAddress.getLocalHost() resolution on OSX Lion when offline
About a month ago, I loaded the Android emulator "Andy" on my windows 8 laptop and it seemed to work fine (except it kept kicking me out of Clash of Clans after a couple minutes, but the emulator kept running).
Yesterday, something happened. While in Clash of Clans, the background turned all black and just the small images were visible. This has happened before and I would kill Andy using the X in the upper right corner. I would then restart Andy and things worked OK again.
However, yesterday when this happened, I killed Andy in the same way, but when I tried to restart Andy the frame would display for a second or two and then go away.
I figured that a bit got twisted somewhere, so I uninstalled that version of Andy and downloaded and installed a newer version, but I get the same results.
I checked the web and the closest I came was "Andy won't launch on windows 8". The suggested solution was to roll back the display driver. I did that with the same results.
I figure that there may be a flag somewhere that thinks Andy is running, so it shuts down any new version, but that is just a guess.
Has anyone else run into this problem?
If so what was the solution?
Try to change the compatibility setting to windows 7/8
Okay, I have just been through a massive amount of bull craparooonie with xcodes new LLDB debugger.
pretty much spent the better most of the day working on an error with my simulator that occurred after updating the debugger to LLDB.. so after figuring it all out I have rolled back to the GDB debugger by changing it in prefrences > edit scheme > debugger back to GDB.
This has solved my issues for now, however I have a question.
Apple are moving to a new set of LLVM suite of tools, I would like to know what I should do, is rolling back to GDB and waiting for a more stable version of LLDB to roll out a good idea? or can you think of something better?
pretty much my question is how best to handle the new upgrading of the xcode tools :)
The best solution is always to use what works the best for you. I also keep GDB active despite xcode complaints. LLDB gives bogus results often.
I've imported an iPhone app that I have developed for iOS and am now maintaining it. I've came across a couple of bugs when trying to add to the iPhone's calendar, which I'm happy to try and sort out myself with a bit of debugging.
One problem is that when I go to run the application on the iPhone simulator, it seems to run an older version of the app than the one I am running. I've removed and added another button since then and the old button is still showing when I run it in the simulator. However, when I compile and run this on a device, it loads the correct version and displays the correct version number in the 'about' view.
But... my main problem is that it doesn't seem to debug on the device properly. The app actually works fine except for the calendar problems, but if I put a few breakpoints in so I can see exactly where this is going wrong, it just doesn't seem to step through! The app pauses, and Xcode says the app has paused! I can press step over and continue execution etc and it appears to work, but I can't see it stepping over the code, nor can I hover over variables to see their values.
I've tried reinstalling Xcode multiple times (I did have a problem installing an older version, so I had to wait until the next version was available before Xcode would install).
The stress is: Today is my last day at work, and I'd really like to get this app ready for iOS 5 before I leave.
Has anyone seen these symptoms before? Is there a debug setting that I've missed? Or is it a corrupted installation?
I wish I could help people a bit with more information, but I don't even know where to start looking here. Any code I can post? any settings? (not too familiar with this, I'm a .NET guy usually).
Thanks!
Sorry you're going through a tough moment there Connell; as you said you're not too familiar with all this, I'm laying down a few steps which might help you out. Some are pretty basic, yes, but I've resolved to these steps myself several times when I've encountered similar scenarios;
If you're testing on the simulator, do a 'Reset Content and Settings' from the 'iOS Simulator' main menu. This will remove all old data and settings and give you a clean start.
Do a 'Clean All Targets' from the Build menu. Then go to your physical project folder and delete the Build folder from it altogether before starting to build again.
Restart both XCode and the Simulator (and your Mac too if possible)
Make sure the mode is set to Debug and not Release or Distribution
Even on the device, remove the old app before putting the new one in, and restart it for good measure.
Delete all Provisioning Profiles from the device and install just the one you need.
On the code;
I've noted that the app appears to 'pause' like this a couple of times when I had accidentally created an infinite loop in the code. Double check to see whether there's something which may cause this.
Unless you haven't already done so, throw an NSLog or two in there to see if its really not being executed beyond the breakpoint.
I've had the exact same problem with a project that I started on xcode 3 and then switched to xcode 4. What fixed it for me was changing the compiler in the project settings.
The default compiler up to xcode 3 was gcc, while the default compiler on xcode 4 is LLVM gcc.
Now, I don't know exactly what's the issue that gdb could have with LLVM gcc, but switching the compiler back to gcc in my project settings and doing a clean build fixed my debugging issues.
Might be worth a try.
Have you checked which debugger is being used GDB or LLDB? Select Edit Scheme from the Product menu, and see what the Debugger setting is under the Debug scheme. You could try switching between GDB, LLDB, and None and running in between.
Something really weird is going on with Xcode and an iPhone project I'm working on, when I'm building for the simulator, the project has 2 active executables (MyApp - iPhone Simulator (2.0) and MyApp - iPhone Simulator (2.1)) Almost all of the time, I want to use the the 2.1 active executable, but Xcode will occasionally silently change to the 2.0 one.
There doesn't seem to be any pattern to this or any trigger that I can notice. Googling has found a couple of people out there who are having the same problem, but no solutions.
Help me stackoverflow-kenobi! You're my only hope!
Ok, it was a bug. The good news: it's fixed in the fresh new 2.2 SDK.
That is weird -- I've been doing iPhone/XCode development for a while, now, and never seen anything like that.
Are you absolutely certain that you're not poking around some place that's causing the change?
Might you have a corrupt XCode or .xcodeproj? If it persists, I'd try re-creating my project and, if that didn't help, reinstalling XCode.
Very strange, indeed...!
I have the same problem. I need to set the active Executable to 2.1 for openAL to work. The pattern I observed is that it switches back everytime I switch to export to the device. Isn't that what happens with you?
I've seen the issue commented a couple of times on the official iphone dev forum, but no solutions. Looks like a bug.
So.. why are you actually doing that? It is probably better, given the nature of the iPhone (with multiple frameworks for multiple architectures), to set up different Targets for your various projects. The executable produced will be the result of the build phases for your targets.