Sorry for not posting a follow up message to the mailing list. I've
been busy :-).
We did much to diagnose the problem, but have not diagnosed the root
cause at this time. We were able to mitigate the problem by disabling
the use of MPM Worker in Apache. We moved to prefork, and have not had
an event since.
We encountered several ways the corruption would be manifested:
Invalid diff stream: insn cannot be decoded
Invalid diff stream: insn overflows the target
Svndiff contains corrupt window header
Missing node-id in node-rev
The invalid diff stream variants were by far the most common.
Factors influencing occurrence of problem were:
Large commits. The larger the commit, the more likely the corruption.
Remote connections. The more remote the connection, the more likely
It's on my todo list to localize the problem and generate a fix, but it
will likely be a month or more before I get back to it. My best *guess*
is that there is a threading issue with Apache or Subversion.
Melikian, Chris wrote:
> Hi Denny,
> Did you solve your problem with the 'Invalid diff stream: insn 0
> cannot be decoded' error which I found at:-
> We've got the same error so if you give us any hints if you have fixed
> it that would be great.
> Chris Melikian
> *Important:* Fidelity Investments International, Fidelity Investment
> Services Limited, Fidelity Pensions Management and Financial
> Administration Services Limited (a Fidelity Group company) are all
> authorised and regulated in the UK by the Financial Services Authority
> and have their registered offices at Oakhill House, 130 Tonbridge
> Road, Hildenborough, Tonbridge, Kent TN11 9DZ. Tel 01732 361144.
> Fidelity only gives information on products and does not give
> investment advice to private clients based on individual
> circumstances. Any comments or statements made are not necessarily
> those of Fidelity. The information transmitted is intended only for
> the person or entity to which it is addressed and may contain
> confidential and/or privileged material. If you received this in
> error, please contact the sender and delete the material from any
> computer. All e-mails sent from or to Fidelity may be subject to our
> monitoring procedures. _Direct link to Fidelity's website._
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Feb 28 07:01:24 2006