You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported in version: HG 2.0 Reported for operating system, platform: Android (All), ARM
Comments on the original bug report:
On 2013-03-30 11:36:04 +0000, Jonny D wrote:
Created attachment 1085
Fix for mIsPaused
I found that the native events thread does not regain control when the app is resumed. This is because onCreate() is called on resume on my device, which sets mIsPaused to false before startApp() releases the semaphore. Attaching patch to move initialization of mIsPaused to the class definition scope.
On 2013-03-31 06:18:36 +0000, Philipp Wiesemann wrote:
If onCreate() is called "on resume" the reason may also be that "android:configChanges" in AndroidManifest.xml [1] does not included all handled changes for the active API level. This attribute may be used to prevent some cases of re-creating everything (for other cases the above patch may still be needed).
Now my question is, after the onStop call...is it "good etiquette" to let the SDL thread keep it's resources (malloc'd stuff, OpenGL textures, etc), or would Android eventually kill the app if we hold on to those resources? (the whole mechanism seems to be triggered on low memory situations).
This bug report was migrated from our old Bugzilla tracker.
These attachments are available in the static archive:
Reported in version: HG 2.0
Reported for operating system, platform: Android (All), ARM
Comments on the original bug report:
On 2013-03-30 11:36:04 +0000, Jonny D wrote:
On 2013-03-31 06:18:36 +0000, Philipp Wiesemann wrote:
On 2013-04-01 09:54:36 +0000, Gabriel Jacobo wrote:
On 2013-04-01 10:57:23 +0000, Philipp Wiesemann wrote:
On 2013-04-08 17:09:02 +0000, Jonny D wrote:
On 2013-04-19 13:41:30 +0000, Gabriel Jacobo wrote:
The text was updated successfully, but these errors were encountered: