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.
Build: NetBeans IDE 7.0 Beta (Build 201011152355) VM: Java HotSpot(TM) 64-Bit Server VM, 17.1-b03, Java(TM) SE Runtime Environment, 1.6.0_22-b04 OS: Windows 7 User Comments: GUEST: aste html code GUEST: I have edited persistance.xml by hand GUEST: nothing, just opened one php file... this sucks redshadow: checking todos, i clicked on an item to open the file and suddenly this came Stacktrace: java.lang.StackOverflowError at org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.getKey(FileChangedManager.java:302) at org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.put(FileChangedManager.java:306) at org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.checkWrite(FileChangedManager.java:113) at org.netbeans.TopSecurityManager.notifyWrite(TopSecurityManager.java:186) at org.netbeans.TopSecurityManager.checkWrite(TopSecurityManager.java:337) at java.io.File.canWrite(File.java:711)
Created attachment 103349 [details] stacktrace
Created attachment 103413 [details] stacktrace Working with a JPanel.
*** Bug 192232 has been marked as a duplicate of this bug. ***
*** Bug 192649 has been marked as a duplicate of this bug. ***
Happens quite often.
ergonomics#a8d72fcfb74f
*** Bug 192447 has been marked as a duplicate of this bug. ***
*** Bug 193051 has been marked as a duplicate of this bug. ***
*** Bug 193048 has been marked as a duplicate of this bug. ***
*** Bug 193085 has been marked as a duplicate of this bug. ***
Integrated into 'main-golden', will be available in build *201012100001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/a8d72fcfb74f User: Jaroslav Tulach <jtulach@netbeans.org> Log: #192504: Refresh change events cannot be synchronous from init(...)
*** Bug 193610 has been marked as a duplicate of this bug. ***
*** Bug 193580 has been marked as a duplicate of this bug. ***