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: | IndexOutOfBoundsException: start=-15 < 0 | ||
---|---|---|---|
Product: | editor | Reporter: | ecerichter |
Component: | Painting & Printing | Assignee: | Miloslav Metelka <mmetelka> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | apric, artur_m, bravo, Debeet, drazisil, Dredd, edjon2000, lehel, mmirilovic, mmolda, vriha, zeloras |
Priority: | P1 | ||
Version: | 7.3 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 197810 |
Attachments: |
stacktrace
stacktrace stacktrace stacktrace |
Description
ecerichter
2013-01-28 03:11:18 UTC
Created attachment 130705 [details]
stacktrace
Maybe 73_HR_FIX #218601 can cause this. Created attachment 131233 [details]
stacktrace
test of php project creating and running
Created attachment 131594 [details]
stacktrace
editing tag file, currently I was trying code completion for import in <%@ tag import>
id #665964 may be helpful, I got stuck in an error loop and was nearly unable to get out. 115 ERs in 3 months ... reproduced also in 7.3.1 looks like regression in recent Dev & ported together with some fix into reelase73 branch Created attachment 133849 [details]
stacktrace
1. Created new php web page
2. select all code (Ctrl + A)
3. pressed delete
4. exception window shows up
Mila, any chance to fix it into 7.3.1 ? (In reply to comment #2) > Maybe 73_HR_FIX #218601 can cause this. Issue #225451 which is integrated in release73 resolves #218601. It's certainly a race condition since unfortunately I can reproduce none of the reproduction steps described in users' reports. So far I've found only one document-lock violation (that might affect the lexer) across php and it's PhpTypedTextInterceptor.afterInsert() but that one is not triggered in case of just selecting all the text and pressing delete. So there must be some other problem. I'll try to add some more asserts across lexer's code together with describing as much context as possible in order to find the problem. I'm sorry, I can't find a way to reproduce it Mila, any progress ? I know it's difficult to fix bugs those we can't reproduce, but this one is rising pretty often and I that's the reason we need to address it in 7.3.1 I guess. *** Bug 224347 has been marked as a duplicate of this bug. *** Unfortunately I'm still not able to reproduce the problem. Yesterday I've fixed issue #227419 but it will likely not eliminate this problem. I'm working on some extra multi-threading tests for the lexer hoping to find the problem. I'm going to simplify the locking mechanism of the lexer in terms of issue #230125 but it will be a large fix that would be too risky for 7.3.1. For 7.3.1 I've made a temporary fix to Token.text() that, in case of IOOBE, it logs the exception and returns an empty string. http://hg.netbeans.org/jet-main/rev/367a0820acae Integrated into 'main-golden', will be available in build *201305252300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/367a0820acae User: Miloslav Metelka <mmetelka@netbeans.org> Log: #225394 - IndexOutOfBoundsException: start=-15 < 0 - temporary fix until lexer locking simplification gets implemented. In release73: 367a0820acae transplanted to eff3439c2d2f Integrated into 'releases', will be available in build *201305262200* or newer. Wait for official and publicly available build. Changeset: http://hg.netbeans.org/releases/rev/eff3439c2d2f User: Miloslav Metelka <mmetelka@netbeans.org> Log: #225394 - IndexOutOfBoundsException: start=-15 < 0 - temporary fix until lexer locking simplification gets implemented. (transplanted from 367a0820acae1b5b93aa4dd12d0d12a2470be55a) verified *** Bug 224771 has been marked as a duplicate of this bug. *** |