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

Bug 370873

Summary:	Batik-based SVG integration must stop processing and dispose objects
Product:	z_Archived	Reporter:	Andi Bur <andi.bur>
Component:	Scout	Assignee:	Project Inbox <scout.core-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	critical
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Andi Bur

2012-02-07 14:14:39 EST

The processing thread created by a Batik JSVGCanvas must be stopped and the widget must be disposed.
Batik BridgeContext objects should be disposed to help cleaning-up the heap.

Comment 1 Andi Bur

2012-02-07 17:58:39 EST

Stop batik's processing thread and dispose any attached BridgeContext objects. The latter implements finalize() and is therefore subject to a Finalizer. Hence the BridgeContext objects are not garbage collected immediately.

Comment 2 Andi Bur

2012-02-23 07:51:07 EST

Migration:
Switch from
  org.eclipse.scout.svg.client.SVGUtility.readSVGDocument(InputStream, boolean)
either to (if no CSS, text size and and bounding box operations are required)
  org.eclipse.scout.svg.client.SVGUtility.readSVGDocument(InputStream)
or to (for performing CSS, text size and and bounding box operations)
  org.eclipse.scout.svg.client.SVGUtility.readSVGDocumentForGraphicalModification(InputStream)
The latter method returns a BridgeContext that must be disposed (BridgeContext.dispose()) when it is
not required anymore. The actual SVG document is referenced by the bridge context as well:
  (SVGDocument) bridgeContext.getDocument()

Comment 3 Matthias Zimmermann

2012-07-09 06:49:34 EDT

ticket closed.
deliverd as part of eclipse scout 3.8.0 (juno release train)