Yes, it sounds like the method cache_simulate_memory_warning_event was never
public (at least I couldn’t find any documentation about it) and Apple started
to enforce its removal. As far as I can tell, a user of JavaFX web cannot fix
this and has currently no chance of publishing a (new?) app to
Sorry, I did a little more digging on this.
My best guess is that Apple is rejecting this because they think you are using
a non-public API of their own.
The OpenJFX version of MemoryPressureHandlerCocoa.mm matches what appears to be
the current WebKit version. [1]
Older versions appear somewh
Odd, but searching shows this used in a different places and nowhere does it
appear anyone has made any changes to the symbol referencing code.
It seems like some applications should of used this same code as-is.
Sort of strange.
I’m done with what digging I think I’m going to do.
GL.
> On Jun 6
Just noticed…
/*
* Copyright (C) 2011-2017 Apple Inc. All Rights Reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyrigh
Nevermind. Found it. Needed to strip the leading _
jfx/modules/javafx.web/src/main/native/Source/WTF/wtf/cocoa/MemoryPressureHandlerCocoa.mm
extern "C" void cache_simulate_memory_warning_event(uint64_t);
void MemoryPressureHandler::platformReleaseMemory(Critical critical)
{
if (critical == C
Try a newer/older version of JavaFX?
I’m not sure which version I cloned jfx off of GitHub but if I search the
directory mentioned in the bug report I find no references to the problem
symbol.
> On Jun 6, 2024, at 2:04 PM, Laurin Murer wrote:
>
> Following up on JDK-8289521 from 2022 and Java
