> I believe I was seeing this way back when I was running in NT and fixed
> it the same way.
That sounds like an bug I found in using Visual C++ to do object oriented
programming. Any time I used the new operator, in VCs compiler it would use
malloc to allocate memory. But malloc has a strange bug that if I allocate
many chunks of memory totaling a small piece of data and free that memory,
and then after that try to allocate many other chunks of memory totaling in a
larger piece of data, it would produce a page fault inside of the malloc
function, on the other hand if I swapped the order in which I allocate a
large chunk of memory, free it, and then allocate a small chunk of memory no
problems would occure. This was a serious problem when loading wavefront obj
files of diffrent sizes. I would first load a game character which was small,
optimize the data structure (sort of like compiling), and then load the
map/level which was largerer and it would cause a page fault. I solved it in
VC by over riding the new operator use GlobalAlloc (I think that is correct)
instead of their buggy version of malloc.
But anyway I dont know what sun is using to compile the native side of java
and java3d, chances are its not VC.
> My current test machine is a 566Mhz Celery. I may switch to the 750Mhz
> machine to see how it reacts to the above settings. I am also tempted
> to put Win98 on my GHz machine to see if it is really an OS thing.
Give that a try to see what happens, but in the end you should resort to the
old fashion debugging, by commenting out big chunks of your code and then
reintroducing pieces of it until the bug shows up again. Narrow down what
might be causing this problem.
What ever the problem may be, it definetly sounds bad, especialy when the
problem is not reproducable and seems random.
Leyland Needham
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
