Android項目覆盤2

我的主頁:chengang.plus/java

文章將會同步到我的微信公衆號:Android部落格android

二、系統數據檢查

2.1 dex更新

咱們開發的java代碼經過編譯生成.class文件,而後經過dx工具生成機器能夠識別的dex文件。數組

Android中採用ClassLoader加載dex文件,加載完成以後能夠經過反射調用其中的方法,適合那些不依賴文件等資源的業務,而打點剛好比較適合使用dex加載的方式。微信

Android中有PathClassLoader和DexClassLoader ,他們都繼承自ClassLoader。他們的繼承關係以下:ide

  • DexClassLoader:能夠加載jar/apk/dex,能夠從SD卡中加載未安裝的apk;
  • PathClassLoader:要傳入系統中apk的存放Path,因此只能加載已經安裝的apk文件。
  • BaseDexClassLoader是DexClassLoader和PathClassLoader的父類,針對傳入不一樣的參數作差別化處理。

看看三個類的源碼:函數

2.1.1 PathClassLoader

dalvik/system/PathClassLoader.java工具

public class PathClassLoader extends BaseDexClassLoader {
    public PathClassLoader(String dexPath, ClassLoader parent) {
        super(dexPath, null, null, parent);
    }
    
    public PathClassLoader(String dexPath, String librarySearchPath, ClassLoader parent) {
        super(dexPath, null, librarySearchPath, parent);
    }
}
複製代碼

2.1.2 DexClassLoader

dalvik/system/DexClassLoader.javaui

public class DexClassLoader extends BaseDexClassLoader {
    public DexClassLoader(String dexPath, String optimizedDirectory, String librarySearchPath, ClassLoader parent) {
        super(dexPath, null, librarySearchPath, parent);
    }
}
複製代碼

2.1.3 BaseDexClassLoader

public class BaseDexClassLoader extends ClassLoader {
    private final DexPathList pathList;
    public BaseDexClassLoader(String dexPath, File optimizedDirectory, String librarySearchPath, ClassLoader parent) {
        this(dexPath, optimizedDirectory, librarySearchPath, parent, false);
    }
    
    public BaseDexClassLoader(String dexPath, File optimizedDirectory, String librarySearchPath, ClassLoader parent, boolean isTrusted) {
        super(parent);
        this.pathList = new DexPathList(this, dexPath, librarySearchPath, null, isTrusted);

        if (reporter != null) {
            reportClassLoaderChain();
        }
    }
    
    public BaseDexClassLoader(ByteBuffer[] dexFiles, ClassLoader parent) {
        // TODO We should support giving this a library search path maybe.
        super(parent);
        this.pathList = new DexPathList(this, dexFiles);
    }
複製代碼

在BaseDexClassLoader中經過DexPathList類具體的處理Dex,他的構造函數以下:this

2.1.4 DexPathList

private Element[] dexElements;
DexPathList(ClassLoader definingContext, String dexPath, String librarySearchPath, File optimizedDirectory, boolean isTrusted) {
    this.dexElements = makeDexElements(splitDexPath(dexPath), optimizedDirectory, suppressedExceptions, definingContext, isTrusted);
}
            
private static Element[] makeDexElements(List<File> files, File optimizedDirectory, List<IOException> suppressedExceptions, ClassLoader loader, boolean isTrusted) {
    Element[] elements = new Element[files.size()];
    int elementsPos = 0;
    for (File file : files) {
        if (file.isDirectory()) {
            elements[elementsPos++] = new Element(file);
        } else if (file.isFile()) {
            String name = file.getName();
            
            DexFile dex = null;
            dex = loadDexFile(file, optimizedDirectory, loader, elements);
        }
    }
    retrun elements;
}

private static DexFile loadDexFile(File file, File optimizedDirectory, ClassLoader loader, Element[] elements) throws IOException {
    if (optimizedDirectory == null) {
        return new DexFile(file, loader, elements);
    } else {
        String optimizedPath = optimizedPathFor(file, optimizedDirectory);
        return DexFile.loadDex(file.getPath(), optimizedPath, 0, loader, elements);
    }
}
複製代碼

最終經過DexFile加載loadDex方法在native層實現對dex的加載和處理。spa

而分析PathClassLoaderDexClassLoader的構造函數能夠看到Android 9.0中的DexClassLoader構造函數的optimizedDirectory參數默認是null。因此這裏要針對版本的不一樣作差別化處理。

咱們通常加載Dex的方式是:

classLoader = context.getClassLoader();
classLoader.loadClass("you class path");
複製代碼

這裏作一下差別化:

public ClassLoader load(Context context,String dexName) {
    mLoaded = false;
    ClassLoader classLoader = null;
    File dexOutputDir = context.getDir("dex", 0);
    File dexFile = new File(dexOutputDir.getAbsolutePath(), dexName);
    Log.d(TAG, "load start");
    if (!dexFile.exists()) {
        return null;
    }
    String dexPath = dexFile.getAbsolutePath();
    Log.d(TAG, "dPath = " + dexPath);
    int version = android.os.Build.VERSION.SDK_INT;
    if (version >= 25) {
        BaseDexClassLoader parent = (BaseDexClassLoader) context.getClassLoader();
        Class<BaseDexClassLoader> c = BaseDexClassLoader.class;
        Method method;
        try {
            method = c.getMethod("addDexPath", String.class);
            method.invoke(parent, dexPath);
            mLoaded = true;
            classLoader = parent;
            return classLoader;
        } catch (Exception e) {
            e.printStackTrace();
        }
    }
    Log.d(TAG, "mLoaded1 = " + mLoaded);
    if (!mLoaded) {
        ArrayList<File> files = new ArrayList<File>();
        files.add(dexFile);

        classLoader = context.getClassLoader();
        classLoader.loadClass("you class path");
        try {
            Field pathListField = findField(classLoader, "pathList");
            Object dexPathList = pathListField.get(classLoader);
            ArrayList<IOException> suppressedExceptions = new ArrayList<IOException>();
            if (version < 19) {
                expandFieldArray(dexPathList, "dexElements",
                        makeDexElements(dexPathList, files, null));
            } else if (version < 23) {
                expandFieldArray(dexPathList, "dexElements",
                        makeDexElements(dexPathList, files, null, suppressedExceptions));
            } else {
                expandFieldArray(dexPathList, "dexElements",
                        makePathElements(dexPathList, files, null, suppressedExceptions));
            }

        } catch (Exception e1) {
            e1.printStackTrace();
        }
    }
    Log.d(TAG, "mLoaded2 = " + mLoaded);
    if (mLoaded) {
        return classLoader;
    }
    return null;
}
複製代碼
  • SDK_INI大於等於25

當sdk_int大於等於25時,經過反射BaseDexClassLoader的addDexPath方法直接添加dex文件到DexPathList的Element[]數組中,然後續findClass方法的邏輯就是遍歷這個數據找到對應的dex文件。

  • SDK_INI小於25

這種狀況下,先反射獲取ClassLoader的pathList對象,這裏的ClassLoader實際是PathClassLoader,可是最終都會到BaseDexClassLoader的pathList。

獲取到這個變量以後,先調用makeDexElements方法將生成的dex對象放到一個數組中,接着在expandFieldArray方法中將就的dex數組和新的dex數組合並:

private Object[] makeDexElements(Object dexPathList, ArrayList<File> files, File optimizedDirectory) throws IllegalAccessException, InvocationTargetException, NoSuchMethodException {
    Method makeDexElements = findMethod(dexPathList, "makeDexElements", ArrayList.class, File.class);

    return (Object[]) makeDexElements.invoke(dexPathList, files, optimizedDirectory);
}
複製代碼

這裏的makeDexElements方法對應的是DexPathListmakeDexElements方法,最終目的是將dex對象添加到Element[]數組中,做爲新的數組返回。

expandFieldArray對應的是DexPathListaddDexPath方法,將新舊Element[]數組合到一個數組中,舊的數組在前面。這樣就致使了相同文件名的dex文件,最新修復了bug的dex不能當即生效。

private void expandFieldArray(Object instance, String fieldName, Object[] extraElements) throws NoSuchFieldException, IllegalArgumentException, IllegalAccessException {
    Field jlrField = findField(instance, fieldName);
    Object[] original = (Object[]) jlrField.get(instance);
    Object[] combined = (Object[]) Array.newInstance(original.getClass()
            .getComponentType(), original.length + extraElements.length);
    System.arraycopy(original, 0, combined, 0, original.length);
    System.arraycopy(extraElements, 0, combined, original.length,
            extraElements.length);
    jlrField.set(instance, combined);
    mLoaded = true;
    Log.d(TAG, "expandFieldArray");
}
複製代碼

對比看下DexPathList中的addDexPath方法:

public void addDexPath(String dexPath, File optimizedDirectory, boolean isTrusted) {
    final List<IOException> suppressedExceptionList = new ArrayList<IOException>();
    final Element[] newElements = makeDexElements(splitDexPath(dexPath), optimizedDirectory,
            suppressedExceptionList, definingContext, isTrusted);
    
    if (newElements != null && newElements.length > 0) {
        final Element[] oldElements = dexElements;
        dexElements = new Element[oldElements.length + newElements.length];
        System.arraycopy(
                oldElements, 0, dexElements, 0, oldElements.length);
        System.arraycopy(
                newElements, 0, dexElements, oldElements.length, newElements.length);
    }
}
複製代碼

可見咱們本身的操做對應着DexPathListaddDexPath方法。

在咱們本身的expandFieldArray方法最後經過執行jlrField.set(instance, combined);,將合併後的Element[]數組賦值給DexPathListElement[] dexElements

當上述操做完成以後,就要調用loadClass方法加載dex文件中的類了,這個方法在ClassLoader類中定義:

protected Class<?> loadClass(String name, boolean resolve) throws ClassNotFoundException
{
    Class<?> c = findLoadedClass(name);
    if (parent != null) {
        c = parent.loadClass(name, false);
    } else {
        c = findBootstrapClassOrNull(name);
    }
    if (c == null) {
        c = findClass(name);
    }
    return c;            
}
複製代碼

parentContext.getClassLoader所屬的PathClassLoader傳遞,一直從BaseDexClassLoaderClassLoader

到這裏要熟悉應用被建立初始化的流程了,這裏先不引伸過去,只須要知道這個parent是BootClassLoader類型。

@Override
protected Class<?> loadClass(String className, boolean resolve)
       throws ClassNotFoundException {
    Class<?> clazz = findLoadedClass(className);

    if (clazz == null) {
        clazz = findClass(className);
    }

    return clazz;
}
複製代碼

若是還找不到,就調用BaseDexClassLoaderfindClass方法了。

@Override
protected Class<?> findClass(String name) throws ClassNotFoundException {
    List<Throwable> suppressedExceptions = new ArrayList<Throwable>();
    Class c = pathList.findClass(name, suppressedExceptions);
    return c;
}
複製代碼

到這裏若是還找不到就拋異常出來了,ClassNotFoundException

上邊的流程就是各大博客上面說的雙親委派機制,父類先從已經加載的類裏面找,找不到的話,再從本身BaseDexClassLoaderfindClass方法裏面去找。

2.1.5 問題覆盤

到這裏,基本就將Dex加載的流程搞清楚了,可是這樣的加載會致使新加載的Dex不能當即生效,必須從新啓動應用以後才能生效。針對這種問題,能夠將Dex熱更新模塊放到一個單獨的進程中,當Dex加載完畢以後,調用killProcess方法自殺,而後由另外一個進程拉活重啓。

相關文章
相關標籤/搜索