I've grepped the relavant lines from what ebook-viewer does:
Code:
Created context:
effective context type: WEB_PAGE
Created context:
effective context type: UNSPECIFIED
Num tracked contexts: 1
Created context:
effective context type: WEB_PAGE
Created context:
effective context type: UNSPECIFIED
Num tracked contexts: 1
Created context:
effective context type: WEB_PAGE
Created context:
effective context type: UNSPECIFIED
Num tracked contexts: 2
Created context:
effective context type: WEB_PAGE
Created context:
effective context type: UNSPECIFIED
Num tracked contexts: 2
Created context:
effective context type: WEB_PAGE
Created context:
effective context type: UNSPECIFIED
Num tracked contexts: 3
Created context:
effective context type: WEB_PAGE
Created context:
effective context type: UNSPECIFIED
Num tracked contexts: 4
Created context:
effective context type: WEB_PAGE
Created context:
effective context type: UNSPECIFIED
Num tracked contexts: 5
Created context:
effective context type: WEB_PAGE
Created context:
effective context type: UNSPECIFIED
Num tracked contexts: 6
Num tracked contexts: 5
Num tracked contexts: 4
Created context:
effective context type: WEB_PAGE
Created context:
effective context type: UNSPECIFIED
Num tracked contexts: 5
Destroyed context for extension
Destroyed context for extension
Destroyed context for extension
Destroyed context for extension
Created context:
effective context type: WEB_PAGE
Created context:
effective context type: UNSPECIFIED
Num tracked contexts: 6
Compared to what quicknanobrowser does:
Code:
Created context:
effective context type: WEBUI
Created context:
effective context type: UNSPECIFIED
Num tracked contexts: 1
Why does ebook-viewer create contexts, destroy them, create them again, etc.? What I've shown above all occurs before the ebook finally appears.
ebook-viewer has several "Destroyed context for extension"s; quicknanobrowser doesn't have those. Is there a memory leak going on?