openjdk6 regression causes finalizers never to be called
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openjdk-6 (Ubuntu) |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
Lucid |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
Precise |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
Quantal |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
Saucy |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
Trusty |
Fix Released
|
Undecided
|
Jamie Strandboge |
Bug Description
Upgrading openjdk6 from 6b27-1.
This is difficult to replicate but we believe it is due to: https:/
This is fixed in b31, and the fix is a one line obviously correct change:
http://
which correctly memset's a structure to zero, as opposed to only setting the first 8 bytes (64 bit) or 4 bytes (32 bit) to zero.
As this is a clear regression caused by an update with a substantial impact (unresolvable memory leaks of objects with finalizers, other resource leaks including FD leaks), I think this is an SRU candidate for Precise (which is where we are seeing it).
tags: | added: precise regression-update |
Changed in openjdk-6 (Ubuntu): | |
status: | Confirmed → Triaged |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in openjdk-6 (Ubuntu Lucid): | |
status: | New → Triaged |
Changed in openjdk-6 (Ubuntu Precise): | |
status: | New → Triaged |
Changed in openjdk-6 (Ubuntu Quantal): | |
status: | New → Triaged |
Changed in openjdk-6 (Ubuntu Saucy): | |
status: | New → Triaged |
Changed in openjdk-6 (Ubuntu Trusty): | |
status: | Fix Committed → In Progress |
Changed in openjdk-6 (Ubuntu Precise): | |
status: | Fix Committed → In Progress |
Changed in openjdk-6 (Ubuntu Trusty): | |
status: | Fix Committed → Fix Released |
https:/ /launchpad. net/ubuntu/ +source/ openjdk- 6/+publishinghi story
confirms that this would have been introduced into Precise on 2014-02-27