cocos2d | The googlecode address | Game Engine library

You are unsing ResolutionPolicy::NO_BORDER with that policy cropping can occur.

NO_BORDER: The entire application fills the specified area, without distortion but possibly with some cropping, while maintaining the original aspect ratio of the application.

When you use SHOW_ALL: The entire application is visible in the specified area without distortion while maintaining the original aspect ratio of the application. Borders can appear on two sides of the application.

Short Answer:

It's a bug in Android 11 fixed by google but not deployed yet.

Meanwhile, if you don't care about calling static and thread_local variables destructors in your lib when program is exiting/library is unloaded, pass the flag -fno-c++-static-destructors to the compiler. (see long answer for a more granular solution using clang annotations)

I used this flag on my project (not cocos2d) with no issue and lib is loading even faster than before.

Long Answer:

Unfortunately this is a performance regression introduced in android 11 (R) by the Google team. The issue is being tracked by google here.

To summarize, when System.loadLibrary() is called, the system registers a destructor for each of the C++ global variables contained in the loaded library, using __cxa_atexit()

Since Android 11 (R), the implementation of this function in android has changed:

• In Q, __cxa_atexit uses a linked list of chunks, and calls mprotect twice on the single chunk to be modified.
• In R, __cxa_atexit calls mprotect twice on a single contiguous array of handlers. Each array entry is 2 pointers.

This change regressed the performance drastically when they are many C++ global variables which seems to be the case in cocos2d so libraries.

Google has already implemented a fix https://android-review.googlesource.com/c/platform/bionic/+/1464716 but as stated in the issue:

this won't be in Android 11 until the March QPR at the earliest, and since this isn't a security issue it won't be mandatory for OEMs to actually take that patch.

Google Team suggests also some workarounds at the app level by removing or skipping the destructors on global variables:

• For a particular global variable, the [[clang::no_destroy]] attribute skips the destructor call.
• Pass -fno-c++-static-destructors to the compiler to skip the destructors for all static variables. This flag also skips destructors for thread_local variables. If there are thread_local variables with important destructors, those can be annotated with [[clang::always_destroy]] to override the compiler flag.
• Pass -Wexit-time-destructors to the compiler to make it warn on every instance of an exit-time destructor, to highlight where the __cxa_atexit registrations are coming from.

With that little info we can't help much. But if I try to interpret the posted image corretly you receive a "EXC_BAD_ACCESS" Exception.

This means more or less that you access a freed memory region or in general you try dereference a pointer pointing to an invalid memory address.

The only argument which could cause such an error is source.c_str(). So you should check the code path of source.

In release builds you don't see always "access-after-free" because memory is not immediately released to the OS (which triggers such errors) it is just marked as "free" to allow faster allocations.

It would seem that LIBAPP is indeed unset. Why that is the case, I don't know. It's dependency, using the same kit and compiler has it set just fine.

Solution I employed is to just set LIBAPP to, in my case, llvm-lib /NOLOGO.

I absolutely hate everything about this.

This is just a basic example. You will have to customize it.

I had to define _WIN32 and _WINDOWS in the project menu of the QtCreator as additional arguments for make to avoid the hardcoding. I also had to define CC_STATIC to prevent Cocos2d to insert the dllimport or dllexport before each of the functions. The arguments I added were:

In most of my apps i use the same syntax and it is working using cocos2d-x version 3.17.2.

Both are same. this->getEventDispatcher() calls CCNode's getEventDispatcher() function. It returns _eventDispatcher.

After some troubles, I found the solution. A GLSL shader that does not have a #version directive at the top is assumed to be 1.10, but I really need version 1.2. So, I need to add '#version 120\n' as a compileTimeHeader string in the initialization: