Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 332418

Summary:

"An internal error occurred during: "Processing Dirty Regions"."

Product:

[WebTools] WTP Source Editing

Reporter:

ltx71cm

Component:

wst.sse

Assignee:

Rakesh <rakes123>

Status:

RESOLVED FIXED

QA Contact:

Nitin Dahyabhai <thatnitind>

Severity:

normal

Priority:

CC:

kentarou, nsand.dev, rakes123

Version:

3.2.2

Flags:

nsand.dev: review+

Target Milestone:

3.2.3

Hardware:

Sun

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
patch	nsand.dev: iplog+

Description ltx71cm

2010-12-13 04:55:19 EST

What steps will reproduce the problem?
1. Unknown

-- Error Details --
Date: Mon Dec 13 03:51:07 CST 2010
Message: An internal error occurred during: "Processing Dirty Regions".
Severity: Error
Product: Eclipse 1.3.1.20100913-1228 (org.eclipse.epp.package.php.product)
Plugin: org.eclipse.core.jobs
Session Data:
eclipse.buildId=M20100909-0800
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.php.product
Command-line arguments:  -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.php.product


Exception Stack Trace:
java.lang.NullPointerException
at org.eclipse.wst.sse.ui.internal.style.SemanticHighlightingReconciler.reconcile(SemanticHighlightingReconciler.java:115)
at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.endProcessing(DocumentRegionProcessor.java:119)
at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor.run(DirtyRegionProcessor.java:682)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Comment 1 Kentarou Fukuda

2010-12-16 08:12:23 EST

Does this bug relate to WST?

Comment 2 Rakesh

2010-12-21 04:52:28 EST

Created attachment 185620 [details]
patch

Although there are no known steps to reproduce this, from stacktrace it is clear that it happens due to null document.Not sure how this got set to null , but a simple check should avoid this problem.

Comment 3 Nick Sandonato

2011-01-12 14:40:38 EST

Code checked into 3.2.3 and HEAD.

Comment 4 Nitin Dahyabhai

2011-01-13 00:10:12 EST

*** Bug 332419 has been marked as a duplicate of this bug. ***