Hi, I am not sure that the following topic is suitable for this mailing list [EMAIL PROTECTED] If it was OK, could you discuss for a while?
Topic How about a little bit widely asking code review around the cache system? Background Many business persons have been reporting the fact that OOo/SO/SS can crash under the following circumstances. User Scenario 1. Open an existing presentation document such as .sxi or .ppt. 2. Create an empty presentation document. 3. Copy many items from the existing document to the new one. 4. Going to two documents back and forth. 5. Eventually, it crashes or an attempt to save a document fails. Some people have noticed the following phenomenon: - An object is occasionally drawn as a different object. - An object is rarely drawn in the different scale. - More amount of objects, more possibilities of crash. There are two concurrent instances of graphic document. The module 'sd' is enforced with a cache system. Apparently, it might be said that a not-yet-hunted racing situation was still hidden around the cache system. Motivations Many professional persons who have been using OOo/SO/SS tend to turn off the automatic document saving system to avoid the situation where they have to repeatedly wait every tens minute until an act of automatic saving a document is finished. Additionally, they tend to have a number of slides in a presentation document that takes much time to be saved into their hard disk. Therefore, they completely loose their presentation document when the problem happens. Best Regards, Tora --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
