CommitMonitor fails to store repository information when a large amount of...

Originally created by: dhorton....@gmail.com
Originally owned by: tortoisesvn

What steps will reproduce the problem?
1. Need a project with large commit logs (> 1024*100 bytes)
2. Run Check Now
3.

What is the expected output? What do you see instead?

Expected: projects to update:

See: If running a DEBUG version, an assert() occurs in 
CSerializeUtils::SaveString(). If running with a RELEASE version the
application silently fails to store data, and projects will not be saved,
nor updated correctly.

What version of the product are you using? On what operating system?
Occurs on both 1.6.4 and latest source ([r460]).

Please provide any additional information below.

My log in this case was 320Kb, so when I changed the various 1024*100
values to 1024*1000 in SerializeUtils the application worked as expected -
updated were saved and persisted between start/stop.

I assume there is a reason for the limits on 1024*100 limit, but
regardless it shouldn't fail silently in the release build.