the garbage collector.
>Does anyone knows a way to avoid this situation?
Fix your code to remove memory leaks. Just because java has garbage
collection does not mean programs can't have memory leaks. If you
keep a reference to an object around, perhaps in a cache or static
variable some p
Title: RE: garbage collection
Alex, IMHO it appears you have a memory leak that is not necessarily a
JVM issue.
But while we are on the GC topic:
Does the 1.4 JVM 'stop the world', or pause *all* threads
while it does a GC. This tends to have a negative impact on
real-time Ja
hi.
We're having a problem with garbage collection in our web site.
We're using JRun with j2sdk 1.4.0 running on a linux machine. The
problem is that after we launch the jrun server the memory starts to
increase up to the maximum heap size defined (1G in our case). When it
re
hi,
I've problem with garbage collection on my linux machine.
Though there are no references pointing to objects in my program,
the memory is not getting released by the JVM on linux machine. When i
run the same program on Solaris machine or WindowsNT machine, the unused
memo
s *INTERRUPTED* flag in the Thread object,
The use of the an instance variable is redundant since the thread already
has
a flag designed for that perpose."
I also think this is a feasible way.
Because I think the root for garbage collection are implementation-dependant.
Depending on th
signed for that perpose."
>
> I also think this is a feasible way.
> Because I think the root for garbage collection are
> implementation-dependant.
> Depending on the implementation and support for native methods,
> roots for garbage collection may be contained in:
>
Thanks very much!
What's your mean:
"which BTW
sets *INTERRUPTED* flag in the Thread object,
The use of the an instance variable is redundant since the thread already
has
a flag designed for that perpose."
I also think this is a feasible way.
Because I think the root for garbage
resources?
That's to say, if I will not need one thread, whether I must stop or
destory it explictly or
just remove it from hashtable for garbage collection?
I am not sure how JVM schedules multiple threads.
Thanks very much!
yangyuexiang
ly or
just remove it from hashtable for garbage collection?
I am not sure how JVM schedules multiple threads.
Thanks very much!
yangyuexiang
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe
d, whether I must stop or
> destory it explictly or
> just remove it from hashtable for garbage collection?
> I am not sure how JVM schedules multiple threads.
Before the Thread can be garbage collected, it must stop
executing. The Java API docs for java.lang.Thread describe the
different
Hi
I have several threads in one hashtable.
When I remove one of them, whether this thread still consume CPU etc
resources?
That's to say, if I will not need one thread, whether I must stop or
destory it explictly or
just remove it from hashtable for garbage collection?
I am not sure ho
On 24 Jan 00, at 10:22, yangyuexiang wrote:
> Who can tell me how to detect the algorithm used in
> JVM for garbage collection?
The correct implementation is not specified and port dependant.
If your questions refers to finding out which algorithm is used in a
specific port, you will h
Who can tell me how to detect the algorithm used in
JVM for garbage collection?
Thanks
yang
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Daniel!
DPZ>How can I tell how much memory an object takes?
There is an article on www.javaworld.com about this topic (it's about clever
memory usage, I don't know the exact title, but there are'nt so many articles
to choose from). Depending on the VM, java.lang.Object takes some 20-30 bytes
and 30 megs in swap and
> > wil stay there all day. This is what I expected in the first place, that
> > the program would grow for awhile until the allocation to Garbage
> > Collection ratio settled out.
> >
> > Is this a know problem in the Linux JDK?
>
> Er
wil stay there all day. This is what I expected in the first place, that
> the program would grow for awhile until the allocation to Garbage
> Collection ratio settled out.
>
> Is this a know problem in the Linux JDK?
Erm... the way to find out about known bugs is to go to
ory and 30 megs in swap and
wil stay there all day. This is what I expected in the first place, that
the program would grow for awhile until the allocation to Garbage
Collection ratio settled out.
Is this a know problem in the Linux JDK?
I have another question that is related to this problem,
I am using the invocation API to start JDK1.2 inside an application
, and everything works fine until System.gc() is called ( or I create
few large arrays and gc() is trigered). The same code works
without problems with JDK117.
The program is using it's own threads, I just attach to the virtual
18 matches
Mail list logo
