|
|
|
Strange. If I clear the log, and reproduce this error, nothing logged to the file. But I attach my log file after restart, because it is long, and I dont understand why exceptions are logged in this file about closed projects in my workspace.... and maybe you can see some useful info in it
I do developing both Java EE and RoR projects, and it would be really hard work (6-8 hrs) if I wanna start all from beginning (with virgin Eclipse) I use Eclipse 3.3.2, Europa, in Ubuntu Dunno what other info could help you, just tell me
I have the same problem. I use Windows Vista, Aptana 1.1, and RadRails 1.0.
You can reproduce this easily with this code. def test Just copy & paste, and then it freeze. Very easy. OK, well this is obviously a pretty big and common problem. We've now got 3 tickets on it and about 5 people who are watching.
The problem really is that I'm unable to reproduce it on my machine. My guess is that I'm not properly passing along encoding somewhere in the process, and it just happens to work for me because I'm on an en_US computer. I'll see if I can fiddle with my language settings or something to try and reproduce this. What encoding is the file you're pasting into? What about the file you are pasting from?
My Eclipse and my files all is in UTF-8.
Try to change the encoding of your eclipse, not only the files... I tried to change the encodig, but it is still freezing ...
I use Korean version of Windows Vista. And .rb file encoding is UTF-8(default).
I think it is necessary for reproducing this problem to install Korean or Japanese language pack. I have the same problem with german umlauts.
Encoding is UTF-8 in Ubuntu 7.10. cwilliams, in case it helps: I am on an en_US.UTF-8 computer, with no language pack but US english (opensuse x86_64, eclipse 3.3.2 w/ Aptana as a plugin).
In order to reproduce I just need to open an empty ruby editor, and type one single accented character. Attaching a .log. Well I've managed to reproduce it on a Japanese version of Windows Vista and Aptana standalone. But here's the problem: I cannot reproduce it if I install Aptana RadRails into Eclipse 3.3 or 3.2.2, and I can't get it to happen underneath the debugger with the source in Eclipse.
I'll have to try downloading all the Aptana and RDT plugins and running the Aptana application under the debugger and see if it'll happen there next. OK. I'm able to reproduce under the debugger now. Thanks torneco, you rock!
Here's the bad news: It looks like this is a bug in JRuby. Before their 1.1 RC2 release they had a huge patch to the paisng code which sped things up a lot. The problem is that they broke parsing of Multibyte strings - it still parsers fine, but the positions it gives back are bad and so are the strings of content they hold onto (for things like comments). That's why we're getting these errors. I've filed a bug with them: http://jira.codehaus.org/browse/JRUBY-2324 I'm also going to try and create a patch so I don't have to wait for their fix. Finally! It's fixed in the 1.0.1 branch. We'll need to do some QA just to make sure, but with this we should be pushing a 1.0.1 build in the next day or two.
To reproduce: Open up RadRails on Japanese Vista. Copy the attached error01-ROR699.rb file and paste it into a new rails project. Double click to open the file. It should now open fine.
it's not released yet. We will notify you when it's released
Thank you, Please check it now. 1.0.1 is released
Thank you, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I can't reproduce this so far. I had to change my encoding to UTF-8 to be able to save the file, but no crashes or anything...