|
Windows has a JVM. Latest version is 1.1, I believe. Also, the pig is probably the application not the JVM. We use it a little, and do not see this problem with our apps. I know sloppy programming has alway been the rule of the PC world, so I would expect this to be true here. I had a program in development do what you are mentioning because I kept loading new socket controls without ever closing the old ones.... Rob Berendt wrote: > I didn't think Windows had a JVM. I thought only via browsers was it >supported. > > jlm@dessertfirst.com on 02/28/2000 05:34:51 PM > Please respond to MIDRANGE-L@midrange.com@Internet > To: MIDRANGE-L@midrange.com@Internet > cc: > Fax to: > Subject: Re: How can Java eat up 160meg of memory? > > >We have an application running on an NT server. It's a pentium pro 200 with > >160meg of memory and 2 2gig scsi hard drives. > > > >Now, this application is "written in Java!!!". First of all, as expected, > >it's a slow running app. but I can deal with that. > > > >The real problem is after only 5 days of running, we have to reboot because > >we get so many "out of memory" errors. this is a machine that needs to be > >24/7. > > > >I can only assume it's the "awesome" builtin cleanup with Java that is > >eating resources like candy. I run my pentium 200mhz PC with 48meg of > >memory for up to 3 weeks at a time and never get memory errors (it just > >reboots itself..haha..). > > > >So, maybe Java cleanup isnt so good? Maybe there is some knowledge of > >memory management needed that this application doesn't use? > > > >I'd be interested in hearing what folks have to say. I'm not saying what > >the software is, though. Maybe if you ask privately I'll tell. ;) This is > >more of a Java gripe than a software gripe, but they do go hand in hand. > >Maybe "written in Java" means to steer clear? 160meg of memory is a LOT of > >memory to eat up in a few days. > > > > Maybe you should try running it on a machine that has a Real Java VM, > instead of MicroSoft's bolluxed-up version? (My opinion.., see Sun's > lawsuit against MS for further details..) > > JLM > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.