16,010,523 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Ron Icard (Top 2 by date)
Ron Icard
20-Jun-11 8:26am
View
Mark, yes I can load the image if it's coming from a file and that doesn't crash. The image I'm getting is from a varbinary(max) field in SQL Server. When I try to call the bmp.SetSource method, it crashes with that "Catastrophic failure" message I listed.
I thought about putting in code to just dump every record to a temporary file and then read that file in to display it so that it doesn't give me the memory error. But, besides being really slow and cumbersome, that will make for some nasty disk cleanup issues that I don't wish to deal with.
I'm REALLY hoping someone else has seen this issue and figured out a work around. Otherwise, I'm dead in the water at the moment.
Ron Icard
16-Jun-11 12:57pm
View
This is a cut and paste of the error from Visual Studio. As I said in the original post, the error occurs in the line:
bmp.SetSource(ms);
Apparently, setting the bitmap image to the memory stream is causing a memory error but I have no clue how to determine what it is or how to fix it.