JDK-4895225 : CMS: Tiger b11: tomcat failed after 2.5 hrs, -server
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 5.0
  • Priority: P1
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2003-07-23
  • Updated: 2003-10-23
  • Resolved: 2003-10-23
Related Reports
Duplicate :  
Description
With tiger b11, when running with CMS GC, on jtg-e450-2.sfbay, Tomcat failed after 0 days: 2 hours 32 minutes
the app was run with -server flag.

> PID: 14854
> Log files under /bt
> 
>   ---- called from signal handler with signal 11 (SIGSEGV) ------
>   [8] MarkRefsIntoAndScanClosure::do_oop(0xf93819d0, 0xee800000,
0x60c4, 0xffffffff, 0xf93819f8, 0xfe661660), at 0xfe38c268
>   [9] objArrayKlass::oop_oop_iterate_nv(0x36, 0xf51547b8, 0xf93819d0,
0x36, 0xfe6613dc, 0x0), at 0xfe5214dc
>   [10]
ScanMarkedObjectsAgainCarefullyClosure::do_object_careful(0xf93819a8,
0xf5154768, 0xdb, 0xf5000e00, 0xc8, 0xd8), at 0xfe38c71c
>   [11]
CompactibleFreeListSpace::object_iterate_mem_careful(0xf5156400,
0xf9381910, 0xf93819a8, 0xf5022c90, 0xf5154768, 0x70), at 0xfe378340
>   [12] CMSCollector::precleanCardTable(0xd55a0, 0xbde90, 0x1, 0xd5670,
0xbe020, 0xb80), at 0xfe3889c4
>   [13] CMSCollector::precleanWork(0xd55a0, 0xfe664040, 0x5b30, 0x47,
0xfe622000, 0x0), at 0xfe387f78
>   [14] CMSCollector::collect_in_background(0xd55a0, 0xfe5c551a,
0xfe687830, 0x1, 0xd57d0, 0x1), at 0xfe384cf0
>   [15] ConcurrentMarkSweepThread::run(0x0, 0x0, 0x7d0, 0xd9a48, 0x1,
0xfe66d168), at 0xfe38f3fc
>   [16] _start(0xd9a48, 0x6c00, 0xfe622000, 0x8, 0xda340, 0x0), at
0xfe266084

core file is saved under /net/jtgb4u4c.sfbay/export/sail7/bigapps_log/solaris/tiger_b11/jtg-e450-2

###@###.### 2003-07-23

Comments
EVALUATION ###@###.### 2003-10-15: With current gc_baseline i am unable to reproduce the failure after a 24+ hour run on the same machine. The contents of gc_baseline as of now will be available in Tiger b25, so please verify that the bug is not reproducible with Tiger b25 and close the bug as "cannot reproduce". For now I am marking this "cannot reproduce yet".
11-06-2004