[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ease-dev] Bug 511888
|
Hi Prashanth,
There are two ways to go about solving a problem like Bug 511888, add
synchronization or redesign the code to not need it.
It is true that synchronization has a performance penalty, but unless
you have profiled the code to demonstrate it is critical performance
wise it is not likely a problem. Deadlock is always a problem to worry
about, but more research into this case will determine if it is a
problem here.
My suspicion is that what is missing is a way to synchronize the read
of the list in org.eclipse.ease.ui.view.ModuleStackDropin$2.getElements(ModuleStackDropin.java:92).
In otherwords are there many writers, or just one. That will determine
the strategy for solving the problem.
HTH
Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com
On 5 March 2017 at 10:55, Prash D <prashanthd912@xxxxxxxxx> wrote:
> Hi Christian,
>
> It's related to Bug 511888.
>
> Is Synchronization a good solution to this problem? However I read it comes
> with several problems. One includes possibility of performance reduction and
> second creation of deadlocks. Will these two cases be relevant in this type
> of code?
>
> Prashanth
>
> _______________________________________________
> ease-dev mailing list
> ease-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/ease-dev
