Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360286 - IOStatementGenerator is not thread safe
Summary: IOStatementGenerator is not thread safe
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-07 17:06 EDT by Justin Spadea CLA
Modified: 2017-02-23 14:16 EST (History)
1 user (show)

See Also:

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 Justin Spadea CLA 2011-10-07 17:06:31 EDT 
If I have a build running for A.egl, and at the same time I have the VE compile a working copy of this file (click refresh on the preview tab), the same instance of an IOStatementGenerator gets used by both concurrent compiles and the last one in "wins" in terms of setting its environment, context, current part, etc.

Either a new instance needs to be created for these contributed statement generators, their usage needs to be synchronized, or all their fields must be made ThreadLocal.
Comment 1 Paul Harmon CLA 2011-10-18 12:37:06 EDT 
I have updated:

Egl2MofStatement
IOStatementGenerator

A new IO statement generator is now instantiated for each IO statement.
Comment 2 Justin Spadea CLA 2011-11-01 16:01:05 EDT 
Verified