On Wed, 21 Jul 1999, Peter Novak wrote:
Halo, I don't know if this is a real bug, but after trying to change display depth in fresh Squeak2.4b.image to depth 2bit, Squeak said that this mode is not supported, but modes in 1bit and other display depths are okay? Is this a bug or it's normal? Why is it not supported (if it okay) ???
I ran into this lousy, 2-bit problem (sorry) a while ago, so I tried testing it on the Mac, Windows, and Unix (Irix).
It seems that it works fine for OS's that support 2-bit screen depths such as the Mac, but it crashes on both Windows and Unix. Specifically, it comes up with a dialog saying "Aborting Squeak!!!! Color depth 2 not supported", and then it aborts Squeak.
I'd say it's definitely a bug that it has to abort Squeak if a 2-bit screen depth isn't supported on a given platform... it should at least do a test so that it doesn't die, and bring up a notifier within Squeak instead.
- Doug Way EAI/Transom Technologies, Ann Arbor, MI http://www.transom.com dway@eai.com, dway@mat.net
It does not crash either 2.4c or 2.5test under Windows -- there is now a test to see if a display depth is supported on the particular platform and a notifier that informs you that it won't work.
-- Dwight
Doug Way wrote:
On Wed, 21 Jul 1999, Peter Novak wrote:
Halo, I don't know if this is a real bug, but after trying to change display depth in fresh Squeak2.4b.image to depth 2bit, Squeak said that this mode is not supported, but modes in 1bit and other display depths are okay? Is this a bug or it's normal? Why is it not supported (if it okay) ???
I ran into this lousy, 2-bit problem (sorry) a while ago, so I tried testing it on the Mac, Windows, and Unix (Irix).
It seems that it works fine for OS's that support 2-bit screen depths such as the Mac, but it crashes on both Windows and Unix. Specifically, it comes up with a dialog saying "Aborting Squeak!!!! Color depth 2 not supported", and then it aborts Squeak.
I'd say it's definitely a bug that it has to abort Squeak if a 2-bit screen depth isn't supported on a given platform... it should at least do a test so that it doesn't die, and bring up a notifier within Squeak instead.
- Doug Way EAI/Transom Technologies, Ann Arbor, MI http://www.transom.com dway@eai.com, dway@mat.net
BUG PROBLEM.
I'm currently running Squeak 2.4b of April 23, 1999, Last update: 1209 on Windows NT.
The application uses a forked process which sits inside a loop waiting for a termination condition to exit. The program is processing a number of HTML based lists and creating a new dynamic output HTML document as a report. It's been very handy and was simple to write.
The peculiar thing is it fails whenever I'm not at my desk. I suspect it's related to something NT is doing while running the screen saver. I get the following message repeating in my console: CreateThread() failed (8) -- Not enough storage is available to process this command. SetThreadPriority() failed (6) -- The handle is invalid.
So what's the deal here? I'm pretty careful about forked processes and do not have any awareness of repeated forks in my code. The only thing is the HTTP stuff in the base image is probably doing some forked stuff. I wonder if there's a resource exhaustion thingy I need to watch for?
The thing that's so frustrating for me about this is that the application was something I crafted to make my own project management duties more efficient. Then a number of other managers have seen this and now before you know it there's a whole bank of people how suddenly depend on good operation 24/7. Of course I didn't see a failure until it was out in front of everyone...
Ideas?
- Steve
At 1:59 PM -0400 7/28/99, Stephan B. Wessels wrote:
[snip]
The application uses a forked process which sits inside a loop waiting for a termination condition to exit. The program is processing a number of HTML based lists and creating a new dynamic output HTML document as a report. It's been very handy and was simple to write.
Are the HTML based lists being downloaded? I.e., are you pulling them off the net, or are they just some local files? And is the process forked so that you can continue working in Squeak in the foreground? Is this Squeak also, e.g., serving files?
The peculiar thing is it fails whenever I'm not at my desk. I suspect it's related to something NT is doing while running the screen saver. I get the following message repeating in my console: CreateThread() failed (8) -- Not enough storage is available to process this command. SetThreadPriority() failed (6) -- The handle is invalid.
This sounds similar to a problem I've had on occasion in Win95 with PWS and a Swiki (on 2.1). I get a sort of white square in the squeak window with these sorts of messages (it's been a while so I don't remember precisely). The circumstances were a *lot* of hits all at once.
You might try keeping a log file to get a better idea of what's happening at the point of failure.
Oh, you said that it only fails "whenever you're not at your desk". Does this mean that if you leave for 5 minutes, it's toast? If your screensaver kicks in for a second, does it go belly up? Is it only overnight that the problem shows up?
Cheers, Bijan Parsia.
squeak-dev@lists.squeakfoundation.org
-
Bijan Parsia -
Doug Way -
Dwight Hughes -
Peter Novak -
Stephan B. Wessels