Skip to content

Crashes on some devices when opening large libraries #5

@CheatBoss

Description

@CheatBoss

Now the application opens the library and loads all its symbols into memory, natively
After that, all the symbols are passed to java through jni calls
The cons of this are:

  1. You are storing the same data in the application memory twice
  2. The jni calls are very slow, taking a very long time to load

To solve this problem, you need to do away with copying data from native to java by doing lazy loading
You need to load symbols only as they appear in the application list, do the search at the native level too, then give the result of the search as a pointer to java

this will fix long loading time and huge memory usage by the application (crashes).

it's also worth using "FastNative" and "CriticalNative" annotations for jni calls, it will make them faster

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions