Community
Participate
Working Groups
Build Identifier: 20100617-1415 I'm working with eclipse-php-helios-win32_20100629.zip and just added FileSync and Subclipse. On a project with about 300 php files, stored locally (with updates copied to a samba server via FileSync plugin), each time, I save a php file after editing, Eclipse hangs and I have to wait about 20 seconds, before I can go on editing my files. With Process Monitor I could see, that during the freeze time there were lots of accesses to .metadata\.plugins\org.eclipse.dltk.core.index.sql.h2\model.lock.db: 15:49:29.9785043 eclipse.exe 300 QueryOpen C:\Apps Data\Eclipse\workspace\.metadata\.plugins\org.eclipse.dltk.core.index.sql.h2\model.lock.db SUCCESS CreationTime: 07.07.2010 15:46:49, LastAccessTime: 07.07.2010 15:46:50, LastWriteTime: 07.07.2010 15:46:50, ChangeTime: 07.07.2010 15:46:50, AllocationSize: 104, EndOfFile: 104, FileAttributes: A 15:49:29.9789127 eclipse.exe 300 CreateFile C:\Apps Data\Eclipse\workspace\.metadata\.plugins\org.eclipse.dltk.core.index.sql.h2\model.lock.db SUCCESS Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: N, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened 15:49:29.9791286 eclipse.exe 300 QueryBasicInformationFile C:\Apps Data\Eclipse\workspace\.metadata\.plugins\org.eclipse.dltk.core.index.sql.h2\model.lock.db SUCCESS CreationTime: 07.07.2010 15:46:49, LastAccessTime: 07.07.2010 15:46:50, LastWriteTime: 07.07.2010 15:46:50, ChangeTime: 07.07.2010 15:46:50, FileAttributes: A 15:49:29.9792659 eclipse.exe 300 CloseFile C:\Apps Data\Eclipse\workspace\.metadata\.plugins\org.eclipse.dltk.core.index.sql.h2\model.lock.db SUCCESS These 4 entries are repeated exactly once per second 17 times with no other file actions from eclipse in between. Reproducible: Always
After consulting with QA, we need to continue the deep performance auditing to complete the fixes for these issues. Also we need others to help us out with reproduction, obviously there are performance bugs that can't be simulated very easily.
I have similar problem. I have java project with one folder containing about 300 sql files. Upon every action with files in this folder (copy, rename, save-after-edit, delete etc) eclipse hangs for minutes with cpu 100%.
*** Bug 319442 has been marked as a duplicate of this bug. ***
Roy: You wrote: >Also we need others to help us out with reproduction, obviously there are >performance bugs that can't be simulated very easily. Test data: I am up for sending some test data. What do you want/Need to reproduce? My project in a ZIP file? Andreas
Eclipse Helios SR 1, Build id 20100917-0705, Win 7, Java1.6_21. (I updated 3.6 using "Help, Check for Updates". While developing a Java SE app, autocomplete freezes for about 20 secs after I type e.g. "obj.a" where "obj" is an instance of a Swing class.
I found a 14G h2 index file in my workspace! The indexing of PHP tool always makes my Eclipse freezing several minutes. I think it does not make sences to have such huge index file. I'm using Kelper M6.
(In reply to comment #6) > I found a 14G h2 index file in my workspace! The indexing of PHP tool always > makes my Eclipse freezing several minutes. I think it does not make sences > to have such huge index file. > > I'm using Kelper M6. I make a habit of clearing the h2 files regularly and I have also updated the stock h2 jar (version 117 if I am not mistaken) with a more recent version from http://www.h2database.com/. See http://devzone.zend.com/1781/five-tips-for-speeding-up-eclipse-pdt-and-zend-studio/.
I haven't these problems on current HEAD. 4 big SF2 projects 2 big SF2 project many other smaller (Kohana, Yii, etc..) Can someone confirm or provide more information?
No answer since year. Marking as fixed. Before reopen make sure you are using latest DLTK and PDT, both have a lot index related improvements.
I am closing this bug as of previous comment. Maybe if there will be a similar problem a new bug should be opened because this one is 5 years old and with much outdated and probably no more relevant information.
