Deadlocks

[tomasoplt]

We are developing Web application which has around 50 states. Some states has about 200 000 records. And Fluxor is in general under heavy load. We are firing around 10 000 actions after application start to fill the stores. In the library is a bug (deadlocks) which appears especially after application start. You have two synchronization objects in classes Store and Dispatcher and they could generate deadlock in some circumstances. After application start when store is not fully initalized and lot of actions is Dispatched lot of deadlocks appears sometimes.

Example:

• you launch first session of web application ( it works )
• second session ( still works )
• after fifth and further sessions server becomes slow and application stuck

We will make some ivestigations and I will try report some progress if we find solution. Bug it would be good, if you could look for this problem also in parallel. It

[mrpmorris]

If you can whittle your app down to as simple a repro project as possible so we can just click a button and wait for the lock that would be useful.

[mrpmorris]

Did it solve your problem?

[tomasoplt]

We have currently our private modified branch. This week we will test your modified version and I will let you know..

[mrpmorris]

Great!

[tomasoplt]

We tested your fix and it's OK. No deadlocks 👍

[mrpmorris]

Excellent. I'll see when I can patch that in to a release.
Thanks for your help!

[mrpmorris]

I have

[mfmadsen]

Hi @mrpmorris, anything I can do to help integrate this fix in a new release? We are seeing the same issue, so are eager to get this fix applied 🙂

[mrpmorris]

@mfmadsen Sorry, I've been busy with work and this slipped my mind.
I'll see if I can get 5.8 released this weekend.

[mfmadsen]

No worries. And thank you so much for an awesome library!

[mrpmorris]

Done!