On Jan 31, 2006, at 4:37 pm, Norman Palardy wrote:
On Jan 31, 2006, at 12:20 PM, Greg wrote:
On Jan 31, 2006, at 1:55 pm, Norman Palardy wrote:
On Jan 31, 2006, at 10:40 AM, Greg wrote:
So I managed to capture a bit of the debugger output surrounding
the windows printing bug which results in:
An UnhandledException in app.exe (GDI32.DLL) 0xC0000005: Access
Violation
Is there anyone at REAL that would be interested in this info?
Also try turning on the task Manager and add the GDI Objects
column to watch
See if you ever go over 10,000 of them
If you do that could be part of the problem
We've done numerous tests in this area and this particular program
doesn't ever seem to get above ~400.
That rules out it being a GDI issue then
Not sure how that can be. The error specifically references GDI32.DLL.
If anyone at REAL is monitoring this thread, I'd really like to know
what it's going to take to fix this bug. Looking back at the
archives, it looks like we've had a rant of one sort or another
regarding the Win32 printing issues each year when a new version of
RB is released. So what's it gonna take? Do I need to purchase a
developer plan? I doubt that this falls under the category of "Quick
Fix", so I'm not inclined to throw my money in that direction.
Greg O'Lone, President
Stretched Out Software
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|