Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P3
Fix Version/s: 8
Affects Version/s: 7u6
Component/s: javafx
Labels:

Subcomponent:
graphics

Currently texture resources are managed separately in at least 2 places depending on how it is used; one is a texture cache for images and the other is the ImagePool for RTTs. This approach is flawed in its design, i.e. the 2 caches are unaware of each other and it assumes system has unlimited native resources.

blocks

JDK-8125895 EGLFB: Occasional SIGSEGV (0xb) in glCopyTexSubImage2D+0x6a10

Closed

duplicates

JDK-8095408 ES2Texture: Need to make immediate disposal of Texture possible

Closed

JDK-8115280 Develop a new native graphics resource handling and garbaging mechanism

Closed

JDK-8124300 Memory leak on change image

Closed

is blocked by

JDK-8090091 image data associated with cached nodes that are removed from a scene are not aggressively released

Open

JDK-8095408 ES2Texture: Need to make immediate disposal of Texture possible

Closed

JDK-8091512 Prism porting layer function to query platform VRAM

Closed

JDK-8102130 Option to track texture memory allocation

Closed

relates to

JDK-8089216 Centralized texture management does not prune unused textures when a platform allocation fails

Open

JDK-8116313 Prism texture pools should wait longer to aggressively free texture memory

Resolved

JDK-8122189 Running with -Dprism.poolstats=true prints warnings about outstanding texture locks

Resolved

JDK-8124300 Memory leak on change image

Closed

JDK-8101914 Centralized resource management should use an aging algorithm to prioritize proactive resource limiting

Resolved

(3 is blocked by, 5 relates to)

Assignee:: Jim Graham

Reporter:: Chien Yang (Inactive)

Votes:: 1 Vote for this issue

Watchers:: 8 Start watching this issue

Created:: 2012-09-27 10:12

Updated:: 2015-06-16 11:06

Resolved:: 2013-04-05 17:39

Imported:: 16/Jun/15 11:03 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates