iPad, v: 18 (iOS) 1.12.23i (11223), p:false java.lang.IllegalStateException: java.lang.Error: Could not allocate texture in time. This could be caused by having too many plugins. In an attempt to recover I disable 10/262 active plugins. Please restart the game to test if it helps. java.lang.IllegalStateException: java.lang.Error: Could not allocate texture in time. This could be caused by having too many plugins. In an attempt to recover I disable 10/262 active plugins. Please restart the game to test if it helps. at info.flowersoft.theotown.stages.LoadingStage.update(LoadingStage.java:1638) at io.blueflower.stapel2d.gamestack.GameStack.update(GameStack.java:154) at info.flowersoft.theotown.TheoTownX.render(TheoTownX.kt:293) at info.flowersoft.theotown.util.ProtectedApplicationAdapter.render(ProtectedApplicationAdapter.kt:28) at com.badlogic.gdx.backends.iosrobovm.IOSGraphics.draw(IOSGraphics.java:275) at com.badlogic.gdx.backends.iosrobovm.IOSGraphics$1.draw(IOSGraphics.java:134) at com.badlogic.gdx.backends.iosrobovm.IOSGraphics$1.$cb$drawRect$(IOSGraphics.java) at org.robovm.apple.uikit.UIApplication.main(Native Method) at org.robovm.apple.uikit.UIApplication.main(UIApplication.java:442) at io.blueflower.theotown.aios.IOSLauncher.main(IOSLauncher.java:300) Caused by: java.lang.Error: Could not allocate texture in time. This could be caused by having too many plugins. In an attempt to recover I disable 10/262 active plugins. Please restart the game to test if it helps. at info.flowersoft.theotown.stages.LoadingStage.lambda$createTexture$10(LoadingStage.java:640) at info.flowersoft.theotown.stages.LoadingStage$$Lambda$22.handle(Unknown Source) at info.flowersoft.theotown.draftloader.PluginHelper.preloadImages(PluginHelper.java:419) at info.flowersoft.theotown.stages.LoadingStage.prefetchImages(LoadingStage.java:374) at info.flowersoft.theotown.stages.LoadingStage$$Lambda$11.run(Unknown Source) at info.flowersoft.theotown.stages.LoadingStage.lambda$update$16(LoadingStage.java:1662) at info.flowersoft.theotown.stages.LoadingStage$$Lambda$28.call(Unknown Source) at java.util.concurrent.FutureTask.run(FutureTask.java:237) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) at java.lang.Thread.run(Thread.java:837)Well, I understand that the crash might be caused due to too many plugins. Now that disabling several plugins is a solution, could you ask me whether I would like to disable plugins first? Why can't I choose not to disable plugins and try again? At least it is wise and reasonable to allow me to select which plugins will be disabled. This mechanism is really frustrating. Please consider removing or optimizing this soon, thanks in advance.
Please Remove or Optimize this Disastrous Recovery Mechanism
- dnswodn
- Inhabitant of a Megacity
- Posts: 253
- Joined: 08 Feb 2022, 08:14
- Location:
Theonia
- Plugins: Showcase Store
-
Plugin Creator
Platform
Please Remove or Optimize this Disastrous Recovery Mechanism
Let me show the crash report first:
- JustAnyone
- Developer
- Posts: 3595
- Joined: 23 Jul 2017, 12:45
- Location: Easter Island
- Plugins: Showcase Store
-
Platform
Re: Please Remove or Optimize this Disastrous Recovery Mechanism
Right now it's a bandaid solution to attempt to recover from the cases where nothing else could be done and the user cannot access the plugins. It takes up to 10 recently downloaded plugins and disables them.