Bug 69675

Summary: Eclipse slow typing
Product: Ports & Packages Reporter: Bjorn Dittmer-Roche <bjorn>
Component: Individual Port(s)Assignee: freebsd-java (Nobody) <java>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Bjorn Dittmer-Roche 2004-07-27 20:10:13 UTC 
      I am working on a large java project in eclipse. Since updating my ports collection recently, i have a problem. When I first start up Eclipse everything is fine. After using it for a bit, most functions continue to work (compiling, running, etc) but when I type it is EXTREMELY slow. For example, I might type a word and the charaters will come out one at time at the rate of about one or two per second. Cutting and pasting seems fine. Also, I often notice that the insertion marker is often not in the same place as where you are typing. It can be off by several pixels and sometimes as much as a charactor.

   Also, possibly related, the new spell check feature seems broken. When I right click on text and select spell check, it loads a page at the bottom that says "Java Spell Checker (Loading...)" and that's it.

How-To-Repeat:       Update eclipse from the ports collection (I used portupgrade). Load a large java project. type and edit for a while. notice that it is painfully slow.
Comment 1 Ying-Chieh Liao freebsd_committer freebsd_triage 2004-07-28 03:09:00 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->java

over to maintainer
Comment 2 Greg Lewis freebsd_committer freebsd_triage 2004-08-02 15:20:49 UTC 
Responsible Changed
From-To: java->freebsd-java

Assign to freebsd-java rather than java.  The longer form is preferred 
and is what all other java@ PRs are assigned to.
Comment 3 Palle Girgensohn freebsd_committer freebsd_triage 2005-02-19 02:26:42 UTC 
Is this still a problem? I cannot reproduce it.

Regards,
Palle
Comment 4 Florent Thoumie freebsd_committer freebsd_triage 2005-06-06 13:23:32 UTC 
State Changed
From-To: open->closed

Feedback timeout. 
This must have been a local problem. 

If I'm wrong closing this PR, please re-open it and accept 
my apologies.