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.

Bug 231020 - !WARNING!! Missing READ-LOCK when accessing TokenHierarchy
Summary: !WARNING!! Missing READ-LOCK when accessing TokenHierarchy
Status: RESOLVED DUPLICATE of bug 226130
Alias: None
Product: javascript
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Petr Pisl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-10 09:35 UTC by Tomas Mysik
Modified: 2013-06-10 10:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Mysik 2013-06-10 09:35:39 UTC 
Just noticed this [1] in my IDE log.

Thanks.

Product Version: NetBeans IDE Dev (Build 20130610-cc611c642aa2)
Java: 1.7.0_21; Java HotSpot(TM) 64-Bit Server VM 23.21-b01
Runtime: Java(TM) SE Runtime Environment 1.7.0_21-b11
System: Linux version 3.8.0-23-generic running on amd64; UTF-8; cs_CZ (nb)

[1]
INFO [org.netbeans.spi.lexer.MutableTextInput]: !!WARNING!! Missing READ-LOCK when accessing TokenHierarchy: input-source:org.netbeans.modules.csl.core.GsfDocument@3aec8c9c, mimeType='text/javascript', kitClass=null, length=537, version=35, file=org.netbeans.modules.csl.core.GsfDataObject@4db1a4f4[/home/gapon/public_html/worx/quizes/app/js/services.js@a106f9f4:7bf6d56d]
java.lang.Exception
        at org.netbeans.lib.lexer.TokenHierarchyOperation.ensureReadLocked(TokenHierarchyOperation.java:397)
        at org.netbeans.lib.lexer.TokenHierarchyOperation.tokenSequence(TokenHierarchyOperation.java:422)
        at org.netbeans.api.lexer.TokenHierarchy.tokenSequence(TokenHierarchy.java:201)
        at org.netbeans.modules.javascript2.editor.api.lexer.LexUtilities.getTokenSequence(LexUtilities.java:125)
Comment 1 Vladimir Riha 2013-06-10 10:19:26 UTC 

*** This bug has been marked as a duplicate of bug 226130 ***