To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=82997 Issue #|82997 Summary|Missing error handling in SalBitmap Component|gsl Version|OOo 2.3 Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|FEATURE Priority|P3 Subcomponent|code Assigned to|pl Reported by|pmladek
------- Additional comments from [EMAIL PROTECTED] Fri Oct 26 10:13:06 +0000 2007 ------- This issue if forked from the issue #82970. We discussed it on irc yesterday. It is pity if OOo crashes when user tries to load a huge picture and there is not enough memory for it. It might also happen when there is a broken file with broken dimensions... We could define some limits into each graphics format file filter. But what should be these limits? I think that the best solution would be to catch this situation directly in X11SalBitmap::ImplCreateDIB when the memory is allocated. Though, it would need to add a proper error handling of this situation. For example, it should not happen that a picture is lost when a document is opened and saved. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
