Bug 448979 - [jdt] BPCE in SemanticHighlightingPresenter.updatePresentation
Summary: [jdt] BPCE in SemanticHighlightingPresenter.updatePresentation
Status: CLOSED DUPLICATE of bug 448980
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-27 11:34 EDT by EPP Error Reports CLA
Modified: 2014-12-10 10:42 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description EPP Error Reports CLA 2014-10-27 11:34:42 EDT
Hello committers,

we received a new error report for Eclipse 4.4.0.I20140606-1215.


General Information:
    anonymous-id:         5222725c-987d-4875-91ce-409270a4a198
    eclipse-build-id:     4.4.0.I20140606-1215
    eclipse-product:      org.eclipse.epp.package.jee.product
    operating system:     Windows8 6.2.0 (x86_64) - win32
    java-runtime-version: 1.8.0_25-b18

The following plug-ins were present on the execution stack (*):
    1. org.eclipse.core.databinding.observable_1.4.1.v20140210-1835
    2. org.eclipse.core.databinding_1.4.1.v20140214-0004
    3. org.eclipse.core.filebuffers_3.5.400.v20140127-1516
    4. org.eclipse.core.runtime_3.10.0.v20140318-2214
    5. org.eclipse.e4.ui.workbench_1.1.0.v20140528-1949
    6. org.eclipse.e4.ui.workbench.swt_0.12.100.v20140530-1436
    7. org.eclipse.equinox.app_1.3.200.v20130910-1609
    8. org.eclipse.equinox.launcher_1.3.0.v20140415-2008
    9. org.eclipse.jdt.ui_3.10.1.v20140817-1500
    10. org.eclipse.jdt_3.10.0.v20140925-0400
    11. org.eclipse.jface.text_3.9.0.v20140521-1657
    12. org.eclipse.jface_3.10.0.v20140604-0740
    13. org.eclipse.swt_3.103.0.v20140605-2008
    14. org.eclipse.ui_3.106.0.v20140519-0906
    15. org.eclipse.ui.ide.application_1.0.500.v20140514-2033
    16. org.eclipse.ui.ide_3.10.0.v20140521-1937


Error Status:

    code:                   10.001
    plugin:                 org.eclipse.jdt.ui_3.10.1.v20140817-1500
    message:                Internal Error
    fingerprint:            75a08d42
    exception class:        org.eclipse.jface.text.BadPositionCategoryException
    exception message:      -
    number of children:     0
    
    org.eclipse.jface.text.BadPositionCategoryException: null
    at org.eclipse.jface.text.AbstractDocument.addPosition(AbstractDocument.java:362)
    at org.eclipse.core.internal.filebuffers.SynchronizableDocument.addPosition(SynchronizableDocument.java:236)
    at org.eclipse.jdt.internal.ui.javaeditor.SemanticHighlightingPresenter.updatePresentation(SemanticHighlightingPresenter.java:414)
    at org.eclipse.jdt.internal.ui.javaeditor.SemanticHighlightingPresenter$1.run(SemanticHighlightingPresenter.java:347)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4147)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3764)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(null:-2)
    at sun.reflect.NativeMethodAccessorImpl.invoke(null:-1)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1)
    at java.lang.reflect.Method.invoke(null:-1)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
   

    

Messages, stacktraces, and nested status objects may be shortened. Please visit 
http://dev.eclipse.org/recommenders/committers/confess/0.5/reports/-
for the complete error log.


Some general information and guidelines about how to use this bug report:

1. Feel free to move this bug to your own product and components. Please note
   that this bug is only accessible to Eclipse committers. If you move this bug
   please make sure that it's still in the "Security Advisor" group.

2. The bug contents of the fields status, resolution, keywords, and whitelist
   are presented to reporters. If you needs more information, please set the
   keyword "needinfo". This will trigger a specialized dialog asking the user
   to provide further details.

3. Use the following resolutions for the following situations:
   * CLOSED / FIXED: This bug has been fixed. Please provide additional
     information in the whiteboard field.
   * CLOSED / WORKSFORME: Use this resolution if you can't reproduce this issue
     and request further information. Please use the whiteboard text to specify
     more details what a user should provide and how.
   * CLOSED / INVALID: Use this resolution if the reported problem is a
     'user-configuration' problem. Please consider giving hints how to fix
     these issues in the whiteboard field.
   * CLOSED / NOT ECLIPSE: Use this if the problem is caused by another plugin
     not developed at Eclipse.org
   * CLOSED / MOVED: If this bug has been moved else where. Please provide more 
     information (e.g. a link) in the whiteboard field.

4. Please remember that only committers can view and comment on this bug. You
   may, however, manually add the reporting user to the bug's cc list. But keep
   in mind that the report may contains sensitive information.

5. If you are missing a feature, please file a enhancement request here:
   https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Recommenders.Incubator&component=Stacktraces
    
 

Thank you for your assistance.
Your friendly error-reports-inbox.


--
* Note: The list of present bundles and their respective versions was
  calculated by package naming heuristics. This may or may not reflect reality.
Comment 1 EPP Error Reports CLA 2014-10-27 11:34:44 EDT
I've looked up the (to date) top-3 most similar bug groups and listed the 
closest bug of each group below. This report may or may not be duplicate of
those (low or similar scores for all entries may indicate that this hasn't
been reported yet):

>     1. Bug 445185: SemanticHighlightingPresenter.updatePresentation causes BadLocationException (err_grp: a7064b8d) – 1    
>     2. Bug 445733: Unhandled event loop exception (err_grp: e2f2d252) – 0,2    
>     3. Bug 448773: [platform] The 'org.eclipse.recommenders.completion.rcp.javaCompletionProposalComputer.i... – 0,2    


If this report actually is a duplicate of those, please mark it as such. This
information helps me to improve the recommendations further for the next issue.

Thank you for your assistance.
Your friendly error-reports-inbox.
Comment 2 Marcel Bruch CLA 2014-12-10 08:07:05 EST
Moving to jdt for review. Not sure whether this is enough information. Please flag as needinfo or close as invalid/worksforme if inappropriate. TY.
Comment 3 Dani Megert CLA 2014-12-10 10:42:03 EST

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