[DMC-944] Remove the buggy davix fork-handler Created: 11/May/17 Updated: 11/May/17 Resolved: 11/May/17
|Project:||DMC - Development|
|Affects Version/s:||davix 0.6.5|
|Fix Version/s:||davix 0.6.6|
|Security Level:||Public Data (This ticket is visible to anyone on the internet and will be indexed by search engines)|
|Reporter:||Georgios Bitzes||Assignee:||Georgios Bitzes|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Apparently, the client application forking at a bad point is quite common.
|Comment by Fabrizio Furano [ 11/May/17 ]|
That's the normality I'd say...
However why remove it instead of fixing ? Was it totally useless ?
|Comment by Georgios Bitzes [ 11/May/17 ]|
My initial idea was that client applications would fork at a reasonable point, ie when there were no threads active inside davix code.
But if the client application forks to ie execv later (which is quite reasonable), it could leave davix in a pretty inconsistent state, and cause memory corruption when the fork-handler runs in the child.
There might be a way to fix it, but since this is rather urgent I'm removing it altogether, and pushing 0.6.6 as soon as possible.