Mantis - Resin
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
3449 | crash | random | 04-16-09 07:21 | 07-22-11 16:15 | |
|
|||||
Reporter: | jkronz | Platform: | |||
Assigned To: | ferg | OS: | |||
Priority: | normal | OS Version: | |||
Status: | closed | Product Version: | 3.1.8 | ||
Product Build: | Resolution: | no change required | |||
Projection: | none | ||||
ETA: | none | Fixed in Version: | 3.1.11 | ||
|
|||||
Summary: | 0003449: Random Crash with *** glibc detected *** double free or corruption (fasttop) in jvm.log | ||||
Description: |
Summary pretty much says it all. Resin will run fine for up to two weeks (average) and then crash. Nothing in any log except a line like: *** glibc detected *** double free or corruption (fasttop) in the jvm log. |
||||
Steps To Reproduce: | |||||
Additional Information: |
We are using Sun's jdk1.6.0_06. This app has been running fine on previous versions of Resin/jdk for years. Also we are binding multiple IP addresses (Resin hosts multiple sites) to one ethernet port through linux IP_ALIASing. I only mention this as the only other even close google match is something to do with JBoss and networking with multiple IP's on one port. Running Debian, all up to date. Crashes always seem to be while the site is under normal load (ie during business hours). Never even close to running out of memory (Note: 0000700MB of 2G used) and the cpu stays below 10% even under our heaviest load. See people suggest using "export MALLOC_CHECK_=0" inside the shell start script to suppress these errors. But obviously, a double free is *not* a good thing to let keep happening and just ignore the error... |
||||
Relationships | |||||
Attached Files: |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|