Good! I have just tried a memory resource monitor and it can be put as a part of portlib to detect the current usage of memory usage. Maybe it can be the first step.:)
On 2/10/07, Rana Dasgupta <[EMAIL PROTECTED]> wrote:
The quick solution sounds great, thanks Jimmy. And opening the JIRA is the right thing to do. On 2/9/07, LvJimmy，Jing <[EMAIL PROTECTED]> wrote: > > Hi All, > I open a new thread for this topic as I'd like to take action for > this. As RI behaves different from Harmony (it never throw that > memory-out-error), it should be a bug of Harmony and we should fix it, > so I open a JIRA, HARMONY-3148 to record this bug and action on it. > Up to now, I see two kinds of solutions: > One solution that is perfect to me is that modify current GC to > handle this native memory , it may use Java heap as native memory, or > try to control native memory as Java heap. But IMHO, this may be a > long way to go to reach this target, requiring long discussion and > well-design for new GC(and VM). > Other poor but quick solution is detect native memory usage in > classlib native code, and call System.gc() if necessary. This is a > fast fix and at least solve part of the problem. A little study on > this solution shows its feasibility and it may not require so much > work as the perfect solution. > So I suggest patch our code with this quick solution in the while, > and if GC gets ready for the perfect solution, we remove this patch. > During this period, more discussion for the design are still welcomed. > Any ideas/suggestions/comments? Thanks. > > -- > > Best Regards! > > Jimmy, Jing Lv > China Software Development Lab, IBM >
-- Leo Li China Software Development Lab, IBM
