Author |
Topic: Cannot Create Screen Bitmap (Read 866 times) |
|
Mystic
Junior Member
member is offline


Gender: 
Posts: 53
|
 |
Re: Cannot Create Screen Bitmap
« Reply #6 on: Jun 2nd, 2015, 3:01pm » |
|
I've been running Task manager and the Resource Monitor while working with my program and it appears to be working as advertised.
Not seeing anything left open when the program closes, etc...
Since it has only happened with one of my users so far I'm guessing he must have something running on his machine that's interfering.
Thanks for all the idea though for things to check.
|
|
Logged
|
- Rick
|
|
|
Richard Russell
Administrator
member is offline


Posts: 1348
|
 |
Re: Cannot Create Screen Bitmap
« Reply #7 on: Jun 2nd, 2015, 3:33pm » |
|
on Jun 2nd, 2015, 3:01pm, Mystic wrote:| I'm guessing he must have something running on his machine that's interfering. |
|
It's possible, but surprising. If a single application is allocating so much bitmap memory - it would need to be 100 Mbytes or more to have that effect - yours is unlikely to be the only program adversely impacted.
Have you confirmed that he's running XP? I would not expect the error to happen on later versions of Windows, which can make available much larger amounts of memory for bitmaps.
Richard.
|
|
Logged
|
|
|
|
Mystic
Junior Member
member is offline


Gender: 
Posts: 53
|
 |
Re: Cannot Create Screen Bitmap
« Reply #8 on: Jun 2nd, 2015, 4:12pm » |
|
All of our work systems are Windows 7 at the moment. I joked with him about running XP, but he is not. This is happening on a Windows 7 machine.
The program has been sent out to about 50 people, and so far he was the only one with a problem, so I'm guessing it's something in the way he has his machine configured.
Maybe he's one of these guys that keeps 100 programs running in the background. <shrug>
|
|
Logged
|
- Rick
|
|
|
Richard Russell
Administrator
member is offline


Posts: 1348
|
 |
Re: Cannot Create Screen Bitmap
« Reply #9 on: Jun 2nd, 2015, 5:31pm » |
|
on Jun 2nd, 2015, 4:12pm, Mystic wrote:| This is happening on a Windows 7 machine. |
|
That's surprising, and might indicate a graphics card/driver issue (my understanding is that the graphics driver is given an opportunity to allocate the bitmap in video memory if available; there is a detailed discussion here). It might be worth checking that the graphics driver is up-to-date.
To put things into perspective, the bitmap that LBB tries to allocate is about 8 Mbytes in size, so even if the system imposed a limit of 256 Mbytes (and in my tests Windows 7 usually doesn't) you could still run about 30 simultaneous LBB programs without hitting the limit.
Incidentally is the machine in question running 32-bits or 64-bits Windows 7? If in doubt, run this program:
Code: if isWin64() then
print "64-bit Windows"
else
print "32-bit Windows"
end if
end
function isWin64()
struct p64, yes as long
calldll #kernel32, "IsWow64Process", _
-1 as long, p64 as struct, r as long
isWin64 = p64.yes.struct
end function Richard.
|
|
Logged
|
|
|
|
|