Closed blizzardengle closed 10 months ago
This issue may be related or the same bug. I notice if I use the phone to fast it triggers these issues quicker just like this comment:
This crash is fairly easy to reproduce:
Open a webview and target something that is easy to do fast back and forth navigation on (example: gmail from the web, entering and exiting emails). Navigate using on screen back buttons embedded into the site (not the device back button).
If you navigate your webview back and forth repeatedly (and quickly) this crash should happen within 50 navigations or so. Sometimes less than 10 navigations. (context)
I used the developer options to run a bug report (bugreport-shiba-UD1A.230803.041-2023-10-27-20-01-38.zip) if someone with GrapheneOS is inserted in the report. Its very personal data so I won't post it here.
This seems connected with https://github.com/GrapheneOS/os-issue-tracker/issues/2601
This seems connected with https://github.com/GrapheneOS/os-issue-tracker/issues/2601
I don't know if they are. They cause a similar problem (symptom) but the abort messages are very different and in my case the crash can be caused by any app not just the launcher.
I have not been able to pin point what the initial trigger is but I have noticed a new issue:
UPDATE: In my testing I have found that sometimes (rarely) I can click through the open app to what is behind it. The app is still open and drawn on the screen but my input is passing through it. I confirmed this by running a few apps until the error occurred, which in turn launched new apps. I double checked and where I had been interacting with the open app was the same location on the home screen of the new app that randomly opened. Again, all i saw was the actual app that I had open but my input was passing through it.
I think there are a cluster of possibly inter-related things. It's not just the launcher which seems to trigger crashes. Other things do as well, including live wallpapers.
Another crashlog I just got:
type: crash
osVersion: google/raven/raven:14/UP1A.231005.007/2023102300:user/release-keys
package: com.android.launcher3:34
process: com.android.launcher3
processUptime: 2062 + 307 ms
android.os.DeadSystemRuntimeException: android.os.DeadSystemException
at android.content.pm.LauncherApps.getApplicationInfo(LauncherApps.java:1081)
at android.content.pm.LauncherApps.loadDrawableResourceFromPackage(LauncherApps.java:1564)
at android.content.pm.LauncherApps.getShortcutIconDrawable(LauncherApps.java:1470)
at com.android.launcher3.icons.ShortcutCachingLogic.getIcon(ShortcutCachingLogic.java:109)
at com.android.launcher3.icons.ShortcutCachingLogic.loadIcon(ShortcutCachingLogic.java:77)
at com.android.launcher3.icons.ShortcutCachingLogic.loadIcon(ShortcutCachingLogic.java:43)
at com.android.launcher3.icons.cache.BaseIconCache.addIconToDBAndMemCache(BaseIconCache.java:324)
at com.android.launcher3.icons.cache.IconCacheUpdateHandler$SerializedIconUpdateTask.run(IconCacheUpdateHandler.java:277)
at android.os.Handler.handleCallback(Handler.java:958)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:294)
at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: android.os.DeadSystemException
... 13 more
This error just happened trying to use the GitHub app:
type: crash
osVersion: google/shiba/shiba:14/UD1A.230803.041/2023102300:user/release-keys
package: com.github.android:754
process: com.github.android
processUptime: 0 + 0 ms
installer: com.android.vending
signal 5 (SIGTRAP), code 1 (TRAP_BRKPT), fault addr 0x0000d1f593e28f2c
Abort message: '[FATAL:aw_draw_fn_impl.cc(113)] Failed GrVkSecondaryCBDrawContext::Make fSecondaryCommandBuffer:0xb400d2d801eeed00 fColorAttachmentIndex:0 fCompatibleRenderPass:0xb400d278167df580 fFormat:37 width:1080 height:2400 is_srgb:1'
backtrace:
#00 pc 00000000045f3f2c /data/app/~~sDO8fw1RoqxfLBtpMAB3Ig==/app.vanadium.trichromelibrary_599311132-csEv6kywYBchddcEZ4wDJQ==/base.apk!libmonochrome_64.so (offset 0x8c0000) (BuildId: 1177265ed36cdcdf99913fee6068aa12d477271b)
#01 pc 000000000220bd30 /data/app/~~sDO8fw1RoqxfLBtpMAB3Ig==/app.vanadium.trichromelibrary_599311132-csEv6kywYBchddcEZ4wDJQ==/base.apk!libmonochrome_64.so (offset 0x8c0000) (BuildId: 1177265ed36cdcdf99913fee6068aa12d477271b)
#02 pc 0000000000010738 /system/lib64/libwebviewchromium_plat_support.so (android::(anonymous namespace)::drawVk(int, void*, android::uirenderer::VkFunctorDrawParams const&, android::uirenderer::WebViewOverlayData const&)+360) (BuildId: 92a13b63494a04d8a28ea92013f438b7)
#03 pc 00000000002b59a4 /system/lib64/libhwui.so (android::uirenderer::WebViewFunctor::drawVk(android::uirenderer::VkFunctorDrawParams const&)+180) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#04 pc 000000000028eb3c /system/lib64/libhwui.so (android::uirenderer::skiapipeline::VkFunctorDrawHandler::draw(GrBackendDrawableInfo const&)+332) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#05 pc 00000000006ad7a8 /system/lib64/libhwui.so (GrVkOpsRenderPass::onExecuteDrawable(std::__1::unique_ptr<SkDrawable::GpuDrawHandler, std::__1::default_delete<SkDrawable::GpuDrawHandler> >)+248) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#06 pc 00000000005a2edc /system/lib64/libhwui.so (GrOpsRenderPass::executeDrawable(std::__1::unique_ptr<SkDrawable::GpuDrawHandler, std::__1::default_delete<SkDrawable::GpuDrawHandler> >)+60) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#07 pc 00000000006593a4 /system/lib64/libhwui.so (skgpu::v1::DrawableOp::onExecute(GrOpFlushState*, SkRect const&)+52) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#08 pc 000000000066da00 /system/lib64/libhwui.so (skgpu::v1::OpsTask::onExecute(GrOpFlushState*)+1040) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#09 pc 000000000058f94c /system/lib64/libhwui.so (GrDrawingManager::flush(SkSpan<GrSurfaceProxy*>, SkSurface::BackendSurfaceAccess, GrFlushInfo const&, skgpu::MutableTextureState const*)+2844) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#10 pc 000000000058fee0 /system/lib64/libhwui.so (GrDrawingManager::flushSurfaces(SkSpan<GrSurfaceProxy*>, SkSurface::BackendSurfaceAccess, GrFlushInfo const&, skgpu::MutableTextureState const*)+160) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#11 pc 00000000005892ec /system/lib64/libhwui.so (GrDirectContextPriv::flushSurfaces(SkSpan<GrSurfaceProxy*>, SkSurface::BackendSurfaceAccess, GrFlushInfo const&, skgpu::MutableTextureState const*)+268) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#12 pc 00000000006c85d4 /system/lib64/libhwui.so (SkSurface_Gpu::onFlush(SkSurface::BackendSurfaceAccess, GrFlushInfo const&, skgpu::MutableTextureState const*)+148) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#13 pc 00000000002996ac /system/lib64/libhwui.so (android::uirenderer::renderthread::VulkanManager::finishFrame(SkSurface*)+284) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#14 pc 000000000028e3b0 /system/lib64/libhwui.so (android::uirenderer::skiapipeline::SkiaVulkanPipeline::draw(android::uirenderer::renderthread::Frame const&, SkRect const&, SkRect const&, android::uirenderer::LightGeometry const&, android::uirenderer::LayerUpdateQueue*, android::uirenderer::Rect const&, bool, android::uirenderer::LightInfo const&, std::__1::vector<android::sp<android::uirenderer::RenderNode>, std::__1::allocator<android::sp<android::uirenderer::RenderNode> > > const&, android::uirenderer::FrameInfoVisualizer*, android::uirenderer::renderthread::HardwareBufferRenderParams const&)+400) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#15 pc 00000000002924f0 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::draw(bool)+768) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#16 pc 000000000029516c /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.__uniq.264041412789356548918088680803242235290.c303f2d2360db58ed70a2d0ac7ed911b)+1324) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#17 pc 00000000002840c0 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+624) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#18 pc 00000000002a66b4 /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+404) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#19 pc 000000000001530c /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+284) (BuildId: 6536c636a18676bd5113fb0378052e1c)
#20 pc 00000000000db93c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
#21 pc 0000000000070570 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
None of this can be replicated by the development team. There's something quite rare about your setup causing it.
@thestinger The issue was so bad I just rest my phone, it was truly unusable. I installed Brave and switched web view (preview?) to it instead of Vanadium. I doubt that was the issue but maybe. I will install Google apps slowly over a few days and see if this happens again.
@thestinger never mind. Brand new install with barely any changes to the phone. Setup pin lock and fingerprint lock. Enabled dark theme. Tried to install Google Play store and Google Services and crash:
type: crash
osVersion: google/shiba/shiba:14/UD1A.230803.041/2023102300:user/release-keys
package: app.grapheneos.apps:21
process: app.grapheneos.apps
processUptime: 0 + 0 ms
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'GrContext is abandoned/device lost at start of CanvasContext::draw'
backtrace:
#00 pc 000000000006eca4 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
#01 pc 000000000064be80 /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+1456) (BuildId: 6ea39c7629f248392ceeb7f63efc9f64)
#02 pc 0000000000044730 /apex/com.android.art/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+80) (BuildId: fe892b2afe1b21a706992b20886336f8)
#03 pc 0000000000011fd4 /system/lib64/liblog.so (__android_log_assert+308) (BuildId: 7b2c8efcf19100c35d7cd5b687e6277a)
#04 pc 0000000000292c04 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::draw(bool)+2580) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#05 pc 000000000029516c /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.__uniq.264041412789356548918088680803242235290.c303f2d2360db58ed70a2d0ac7ed911b)+1324) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#06 pc 00000000002840c0 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+624) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#07 pc 00000000002a66b4 /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+404) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#08 pc 000000000001530c /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+284) (BuildId: 6536c636a18676bd5113fb0378052e1c)
#09 pc 00000000000db93c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
#10 pc 0000000000070570 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
I use my phone quickly, is that an issue? I think I swiped the notification drawer down to clear things as soon as I started the download, then swiped over to open apps to clear them (I think it was just Settings and Files that was open), before trying to reopen the App app. All that was in like 3 seconds and this crash happened.
Your phone seems to have a hardware issue. I can't think of another explanation.
Your phone seems to have a hardware issue. I can't think of another explanation.
TL;DR I disagree since the stock os works, but I understand that its a edge case for sure.
I used the phone with the stock OS for a while before factory resetting it and putting Graphene on it. I just reverted back to the stock OS and after a 30 minute stress test I can't reproduce these issues on stock.
I don't know why this only happens on Graphene. My educated guess is maybe I have an earlier production run model with slight different hardware? Either way I am returning the phone. I have a Pixel 6a that has been running Graphene flawlessly for months with the exact same setup apps/permissions wise; for the curious, no I did not load a backup, I manually setup all the apps/permissions on the Pixel 8.
@thestinger I'm leaving this issue open for now just in case someone else runs into this problem, but since I'm returning the phone I understand if you need to mark it closed.
@blizzardengle If you install GrapheneOS again and don't install a bunch of apps, make configuration changes, etc. do you have the problem?
@thestinger yes, but here is the full story:
Since everything appeared good on stock, I factory reset, and then setup everything (apps/permissions) right out of the gate on Graphene and noticed these issues within the first 4-6hrs of use I would say. Then the phone just became unusable. I would have to restart it after 10 minutes of use.
To double check everything, I factory reset again, and used Graphene stock for a few minutes; opened Settings, App, File, and Calculator. Couldn't trigger the issue. As soon I started to install Google Play Store and Google Play Services it started happening again; which was weird to me because I hadn't even tried to install a Play store app yet and previously it didn't happen that fast. That was this crash:
type: crash
osVersion: google/shiba/shiba:14/UD1A.230803.041/2023102300:user/release-keys
package: app.grapheneos.apps:21
process: app.grapheneos.apps
processUptime: 0 + 0 ms
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'GrContext is abandoned/device lost at start of CanvasContext::draw'
backtrace:
#00 pc 000000000006eca4 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
#01 pc 000000000064be80 /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+1456) (BuildId: 6ea39c7629f248392ceeb7f63efc9f64)
#02 pc 0000000000044730 /apex/com.android.art/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+80) (BuildId: fe892b2afe1b21a706992b20886336f8)
#03 pc 0000000000011fd4 /system/lib64/liblog.so (__android_log_assert+308) (BuildId: 7b2c8efcf19100c35d7cd5b687e6277a)
#04 pc 0000000000292c04 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::draw(bool)+2580) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#05 pc 000000000029516c /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.__uniq.264041412789356548918088680803242235290.c303f2d2360db58ed70a2d0ac7ed911b)+1324) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#06 pc 00000000002840c0 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+624) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#07 pc 00000000002a66b4 /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+404) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#08 pc 000000000001530c /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+284) (BuildId: 6536c636a18676bd5113fb0378052e1c)
#09 pc 00000000000db93c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
#10 pc 0000000000070570 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
Factory reset again, reverted to stock android, and stressed tested for 30 minutes. I installed tons of apps, opened every app I could, typed into multiple keyboards, force killed apps, ect. I could not reproduce this on the stock os.
You're doing something rare other people aren't doing that's causing it. If you won't narrow that down, we can't help.
If you narrow down what's causing it, perhaps we can resolve it.
I don't know how to narrow that down. Here is a full breakdown roughly in order:
Attempt 1: Initial Install of Graphene
Attempt 2: Clean Install of Graphene
type: crash
osVersion: google/shiba/shiba:14/UD1A.230803.041/2023102300:user/release-keys
package: app.grapheneos.apps:21
process: app.grapheneos.apps
processUptime: 0 + 0 ms
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'GrContext is abandoned/device lost at start of CanvasContext::draw'
backtrace:
#00 pc 000000000006eca4 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
#01 pc 000000000064be80 /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+1456) (BuildId: 6ea39c7629f248392ceeb7f63efc9f64)
#02 pc 0000000000044730 /apex/com.android.art/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+80) (BuildId: fe892b2afe1b21a706992b20886336f8)
#03 pc 0000000000011fd4 /system/lib64/liblog.so (__android_log_assert+308) (BuildId: 7b2c8efcf19100c35d7cd5b687e6277a)
#04 pc 0000000000292c04 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::draw(bool)+2580) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#05 pc 000000000029516c /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.__uniq.264041412789356548918088680803242235290.c303f2d2360db58ed70a2d0ac7ed911b)+1324) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#06 pc 00000000002840c0 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+624) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#07 pc 00000000002a66b4 /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+404) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#08 pc 000000000001530c /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+284) (BuildId: 6536c636a18676bd5113fb0378052e1c)
#09 pc 00000000000db93c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
#10 pc 0000000000070570 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
This was a clean install of Graphene. I restarted all the installs for Google Play Store and Services after dismissing the error and NEVER removed the sensor permission from anything like I had done in the first attempt. I played with the phone for a bit and issues started manifesting again even without installing a single Google app. I think I installed Gmail and Voice after this to keep testing and all the errors/crashes were present again.
Attempt 3: Clean Install of Stock
This is honesty the best I can do to help.
I have a bug report recorded by the phone when I was using Graphene if you have a private email I can send it to?
TL;DR I did everything listed below and everything seemed ok at first but then I started getting crashes again. The crashes even happened unassisted --> When my alarms went off in the morning they only lasted ~5 seconds before triggering the same crash
type: crash
osVersion: google/shiba/shiba:14/UD1A.230803.041/2023102300:user/release-keys
package: com.android.launcher3:34
process: com.android.launcher3
processUptime: 0 + 0 ms
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'GrContext is abandoned/device lost at start of CanvasContext::draw'
backtrace:
#00 pc 000000000006eca4 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
#01 pc 000000000064be80 /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+1456) (BuildId: 6ea39c7629f248392ceeb7f63efc9f64)
#02 pc 0000000000044730 /apex/com.android.art/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+80) (BuildId: fe892b2afe1b21a706992b20886336f8)
#03 pc 0000000000011fd4 /system/lib64/liblog.so (__android_log_assert+308) (BuildId: 7b2c8efcf19100c35d7cd5b687e6277a)
#04 pc 0000000000292c04 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::draw(bool)+2580) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#05 pc 000000000029516c /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.__uniq.264041412789356548918088680803242235290.c303f2d2360db58ed70a2d0ac7ed911b)+1324) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#06 pc 00000000002840c0 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+624) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#07 pc 00000000002a66b4 /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+404) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#08 pc 000000000001530c /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+284) (BuildId: 6536c636a18676bd5113fb0378052e1c)
#09 pc 00000000000db93c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
#10 pc 0000000000070570 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
UPDATES
After getting some food and refocusing I had these thoughts:
With this in mind I decided to track every little thing I do to see if I could replicate this issue. I flashed the stock os again, made sure the phone was working, and then restarted from scratch the install of Graphene, but this time:
Debug Session
I can not pin point what the root cause is. Using stock Graphene with no other apps rarely triggers this issue, it is only after installing Google Services, Framework, and Play Store that the issue becomes more noticeable; and this is without any other apps added yet. Adding only 7 apps and testing here is my observations:
Debug Session
Closing Thoughts
Maybe I got a lemon. I will keep the phone for 1 more day in case anyone has specific ideas of what to test, but tomorrow I'm flashing stock back on and returning it. Aside: I have abused and stressed tested my Pixel 6a with Graphene for ~3 months with no issues. If I have some rare workflow surely I would have bricked that phone long ago.
Hi all, I am running into this same issue where the phone will freeze and require a hard reset. It mostly happens while I am on a walk where I will be playing music/podcasts over bluetooth and have my flashlight on, but it has happened randomly as well. Any app that is open (even settings, launcher, and systemui) will crash and include this in the error message:
Abort message: 'GrContext is abandoned/device lost at start of CanvasContext::draw'.
Looking through the comments, I will note that I do not have GPlay services/store installed, but I did have them at one point to download an eSIM.
This issue doesn't occur on my Pixel 7Pro.
Edit: The crash will often turn off my flashlight, but not the music playing.
type: crash
osVersion: google/shiba/shiba:14/UD1A.230803.041/2023102300:user/release-keys
package: com.android.settings.intelligence:34
process: com.android.settings.intelligence
processUptime: 0 + 0 ms
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'GrContext is abandoned/device lost at start of CanvasContext::draw'
backtrace:
#00 pc 000000000006eca4 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
#01 pc 000000000064be80 /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+1456) (BuildId: 6ea39c7629f248392ceeb7f63efc9f64)
#02 pc 0000000000044730 /apex/com.android.art/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+80) (BuildId: fe892b2afe1b21a706992b20886336f8)
#03 pc 0000000000011fd4 /system/lib64/liblog.so (__android_log_assert+308) (BuildId: 7b2c8efcf19100c35d7cd5b687e6277a)
#04 pc 0000000000292c04 /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::draw(bool)+2580) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#05 pc 000000000029516c /system/lib64/libhwui.so (std::__1::__function::__func<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0, std::__1::allocator<android::uirenderer::renderthread::DrawFrameTask::postAndWait()::$_0>, void ()>::operator()() (.__uniq.264041412789356548918088680803242235290.c303f2d2360db58ed70a2d0ac7ed911b)+1324) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#06 pc 00000000002840c0 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+624) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#07 pc 00000000002a66b4 /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+404) (BuildId: 56a6ea38174b012e1e73074e7c0a4b2e)
#08 pc 000000000001530c /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+284) (BuildId: 6536c636a18676bd5113fb0378052e1c)
#09 pc 00000000000db93c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
#10 pc 0000000000070570 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 70e39a6810cd2a8f7b6f23f9b5ea610d)
Hi all, I am running into this same issue where the phone will freeze and require a hard reset...
Abort message: 'GrContext is abandoned/device lost at start of CanvasContext::draw'.
Edit: The crash will often turn off my flashlight, but not the music playing.
@mattinahat13 I'm sorry to hear your having the same issue but I'm relieved to know its not just my phone. I can confirm my crashes have been similar to yours; music will still play for example.
I really think there might be some regression issue related/similar to this graphics bug in Android. Maybe some phones have different versions (iterations) of the hardware like the GPU.
Just want to add my recent experience with the Pixel 5A and perhaps the latest GOS (not sure about the exact version, but I updated as soon as the update was available). The phone is currently dead - black screen, doesn't react to power button / power button + volume down / charger plugged in.
The point I wanted to make is following - the phone (the screen) froze three times before it died. For a first time (yesterday) when watching video using Brave. Then after some attempts I managed to restart the phone. This morning happened it for a second time. The phone (screen) froze, then I managed to restart it with a long press of the power button. And for a third time an hour later I wasn't that lucky anymore, the phone didn't (re)start.
Few days ago I got some error log after an update (sorry, not possible to get it anymore) and system pop-up messages saying that some app needs to restart.
Sorry for the vague fashion of the report, but the phone is dead and I am unable to grab any data from it. I am pretty confident the issue is not hardware related, but has something to do with the previous freezes as they immediately led to the current condition. The battery should not be an issue, it was fully charged this morning. I am pretty sad.
@detabc That's 100% guaranteed to be a hardware issue and not relevant to this.
Is this still an issue with the November update?
Is this still an issue with the November update?
I returned my Pixel 8. @mattinahat13 ?
Sorry, haven't been logged in, but yes, the issue is still persisting. Notably the phone is very stable on wi-fi. Tried removing the eSIM but still getting the issue. Been reflashing the OS and running factory resets now and again, but can't pinpoint the exact cause for this issue.
@mattinahat13 Please open a new issue since it's not necessarily the same problem.
Im actually experiencing the same issue described. Even after yesterday's update. I posted on the forum, and it seemed to be an upstream bug
https://discuss.grapheneos.org/d/9030-apps-crash-on-pixel-8-pro
Is there anything i can do to help debug this? As opposed to OP, returning the phone is not really an option and id like to have a working phone.
Please open a new issue.
I have to constantly restart my Pixel 8 because it eventually becomes unusable. The keyboard constantly locks up or crashes and multiple apps do the same. The launcher constantly crashes and just sliding down the app drawer will trigger a crash sometimes. The date and time bar will disappear as well. Now the screen just flashes on and off as I try to navigate around; it appears its crashing and recovering in a loop. Here are some but not all of the errors I have been able to record; sometimes the phones crashes and I cant copy the error.
For context I do have Google apps installed and Play Store and Play Services installed with as minimal permissions as I can. I also have removed the
sensors
permission from just about everything I have installed.UPDATE: In my testing I have found that sometimes (rarely) I can click through the open app to what is behind it. The app is still open and drawn on the screen but my input is passing through it. I confirmed this by running a few apps until the error occurred, which in turn launched new apps. I double checked and where I had been interacting with the open app was the same location on the home screen of the new app that randomly opened. Again, all I saw was the actual app that I had open but my input was passing through it.
This error looks unrelated to the above but it's the latest I have been able to grab: