This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | ArrayIndexOutOfBoundsException in System.arraycopy | ||
---|---|---|---|
Product: | utilities | Reporter: | _ proxity <proxity> |
Component: | Properties | Assignee: | Jan Stola <jstola> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | Keywords: | THREAD |
Priority: | P2 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Screenshot of situation during display of exception
See ide.log for version information |
Description
_ proxity
2004-04-20 12:55:23 UTC
Created attachment 14475 [details]
Screenshot of situation during display of exception
I suspect a problem with the escaping of the # comment sign which is in the value. It seems that problem can be always triggered by simply adding " #" (space + #) to the end of a key! I am not able to reproduce the exception. Boris, could you please describe the exact steps on how to make the exception to be thrown? Thank you. This bug may be related to bug #41885 ("Table-view editor cannot save keys containing space"). E.g. open a properties file, create a new property with key "a #" and value "b". This causes mysterious things with the entered data. With or without exception. OK, I did it. I opened an already existing .properties file by double-clicking on its node in the NetBeans explorer window. The table editor was opened. Then I clicked on the New Property... and entered key "a #" and value "b" into the dialog. I pressed the OK button in the dialog. In the table, a new entry was added, having key "a" and value "#=b" which is wrong but it is caused by the known bug #41885. However, I cannot see the exception. If you are able to reproduce the bug with a simple .properties file, please attach it to this bug report. Are you using the final version of NetBeans 3.6? Which JDK are you using? Created attachment 14483 [details]
See ide.log for version information
Thank you. You have the same version of both NetBeans and JDK as me. The only difference is that you have a different version of Linux kernel and (probably) a different hardware. It seems the problem is with synchronization of threads. It may have same or similar cause as bug #34436 ("ConcurrentModificationException on resource file editing"). I have not been able to reproduce any of the bugs but their existence is apparent from the exception call stacks. The reporter uses a multiprocessor machine - it is the probable reason why I could not reproduce it (on a single-processor machine). Exception happened again. I inserted only a missing 'n' in a value of a resource bundle. No sorry, it was the key field. I tried it again and bug #34436 happened. Please fix that stuff. To me the Resource Editor is totally unusable in 3.6 Lowering the priority - the exception seems to be extremely rare on a single-processor machine. On a SMP machine this happens very often. The properties editor is unusable for me now. Please check for missing synchronization. This issue is not reproducible on single-processor machine => lowering priority to P3. Please, don't change priorities inappropriately. We understand that it is an important problem for you, but the priority must be objective and should not track someones' feelings. If you program in multiple threads you have to bear the consequences. Do you need a SMP machine to test your software? I agree with the reporter that this bug should have a higher priority if it prevents using the basic module's functionality. Multiprocessor machines are not extraordinary and the module should work on such machines. This issue seems to be similar to the issue 34436. The root of the exception seems to be again a missing synchronization of the method BundleStructure.buildKeySet() and the fact that the field BundleStructure.keyList is modified directly (it is better to replace it when a new list is completed). I implemented both mentioned changes, so the problem should be fixed. Unfortunately I was not able to reproduce this problem even before this fix (its probability is much lower then the probability of the issue 34436). On the other hand the "steps to reproduce" and the attached snapshot support the mentioned scenario. If you want to verify/ensure that this bug is fixed, you can download the latest development build of Netbeans 4.0 from http://www.netbeans.info/downloads/download.php?a=n&p=1 Note that the first build that contains this fix is 21 July, 18:00 200407211800 4.0 daily build. Feel free to reopen this issue if you are still able to reproduce it. Verified on a 2cpu Optetron mashine, in nb200507181000. |