4 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

Excuse my language, but:

enter image description here

When hotfixing a similar bughotfixing a similar bug caused this to show up for more users, it came me as a great hint to what was causing it. Basically, we were trying to hardware accelerate all of our views and some GPUs just don't have big enough storage to handle how hilariously complex the WebViews we use for displaying posts are. Due to my ignorance, I had tried to fix this by setting the views to LAYER_TYPE_SOFTWARE which, you know, kind of sounds like the opposite of LAYER_TYPE_HARDWARE, but it turns out that they both use bitmap buffers and sometimes we still go over that limit!

So long story short, starting from version 1.0.59 (coming out sometime tomorrow, some other minor bugs I want to fix before that release) we finally have this issue fixed. If you're on a device that's running a version of Android lower than 5.0*, the posts will be using LAYER_TYPE_NONE which doesn't try to generate a bitmap of the view, and bam now posts are readable on devices with lower end GPUs. I'm psyched. I'm so sorry it took this long to fix it (and so sorry about the lack of communication, this bug has been driving me crazy and I didn't want to post until I knew exactly what was happening).


* We're currently doing the test off 5.0 because I suspect this issue only happens on WebKit powered WebViews (5.0 switched over to a Chromium powered WebView) -- If it keeps happening on 5.0 or above I'll modify that condition to be something else. Sadly you can't just say "If this device has a GPU with a small buffer", but "if this device has a high res screen" is a good alternative test we might switch over too.

Excuse my language, but:

enter image description here

When hotfixing a similar bug caused this to show up for more users, it came me as a great hint to what was causing it. Basically, we were trying to hardware accelerate all of our views and some GPUs just don't have big enough storage to handle how hilariously complex the WebViews we use for displaying posts are. Due to my ignorance, I had tried to fix this by setting the views to LAYER_TYPE_SOFTWARE which, you know, kind of sounds like the opposite of LAYER_TYPE_HARDWARE, but it turns out that they both use bitmap buffers and sometimes we still go over that limit!

So long story short, starting from version 1.0.59 (coming out sometime tomorrow, some other minor bugs I want to fix before that release) we finally have this issue fixed. If you're on a device that's running a version of Android lower than 5.0*, the posts will be using LAYER_TYPE_NONE which doesn't try to generate a bitmap of the view, and bam now posts are readable on devices with lower end GPUs. I'm psyched. I'm so sorry it took this long to fix it (and so sorry about the lack of communication, this bug has been driving me crazy and I didn't want to post until I knew exactly what was happening).


* We're currently doing the test off 5.0 because I suspect this issue only happens on WebKit powered WebViews (5.0 switched over to a Chromium powered WebView) -- If it keeps happening on 5.0 or above I'll modify that condition to be something else. Sadly you can't just say "If this device has a GPU with a small buffer", but "if this device has a high res screen" is a good alternative test we might switch over too.

Excuse my language, but:

enter image description here

When hotfixing a similar bug caused this to show up for more users, it came me as a great hint to what was causing it. Basically, we were trying to hardware accelerate all of our views and some GPUs just don't have big enough storage to handle how hilariously complex the WebViews we use for displaying posts are. Due to my ignorance, I had tried to fix this by setting the views to LAYER_TYPE_SOFTWARE which, you know, kind of sounds like the opposite of LAYER_TYPE_HARDWARE, but it turns out that they both use bitmap buffers and sometimes we still go over that limit!

So long story short, starting from version 1.0.59 (coming out sometime tomorrow, some other minor bugs I want to fix before that release) we finally have this issue fixed. If you're on a device that's running a version of Android lower than 5.0*, the posts will be using LAYER_TYPE_NONE which doesn't try to generate a bitmap of the view, and bam now posts are readable on devices with lower end GPUs. I'm psyched. I'm so sorry it took this long to fix it (and so sorry about the lack of communication, this bug has been driving me crazy and I didn't want to post until I knew exactly what was happening).


* We're currently doing the test off 5.0 because I suspect this issue only happens on WebKit powered WebViews (5.0 switched over to a Chromium powered WebView) -- If it keeps happening on 5.0 or above I'll modify that condition to be something else. Sadly you can't just say "If this device has a GPU with a small buffer", but "if this device has a high res screen" is a good alternative test we might switch over too.

3 We're in alpha again? Aww. :(
source | link

Excuse my language, but:

enter image description here

When hotfixing a similar bug caused this to show up for more users, it came me as a great hint to what was causing it. Basically, we were trying to hardware accelerate all of our views and some GPUs just don't have big enough storage to handle how hilariously complex the WebViews we use for displaying posts are. Due to my ignorance, I had tried to fix this by setting the views to LAYER_TYPE_SOFTWARE which, you know, kind of sounds like the opposite of LAYER_TYPE_HARDWARE, but it turns out that they both use bitmap buffers and sometimes we still go over that limit!

So long story short, starting from version 01.10.59 (coming out sometime tomorrow, some other minor bugs I want to fix before that release) we finally have this issue fixed. If you're on a device that's running a version of Android lower than 5.0*, the posts will be using LAYER_TYPE_NONE which doesn't try to generate a bitmap of the view, and bam now posts are readable on devices with lower end GPUs. I'm psyched. I'm so sorry it took this long to fix it (and so sorry about the lack of communication, this bug has been driving me crazy and I didn't want to post until I knew exactly what was happening).


* We're currently doing the test off 5.0 because I suspect this issue only happens on WebKit powered WebViews (5.0 switched over to a Chromium powered WebView) -- If it keeps happening on 5.0 or above I'll modify that condition to be something else. Sadly you can't just say "If this device has a GPU with a small buffer", but "if this device has a high res screen" is a good alternative test we might switch over too.

Excuse my language, but:

enter image description here

When hotfixing a similar bug caused this to show up for more users, it came me as a great hint to what was causing it. Basically, we were trying to hardware accelerate all of our views and some GPUs just don't have big enough storage to handle how hilariously complex the WebViews we use for displaying posts are. Due to my ignorance, I had tried to fix this by setting the views to LAYER_TYPE_SOFTWARE which, you know, kind of sounds like the opposite of LAYER_TYPE_HARDWARE, but it turns out that they both use bitmap buffers and sometimes we still go over that limit!

So long story short, starting from version 0.1.59 (coming out sometime tomorrow, some other minor bugs I want to fix before that release) we finally have this issue fixed. If you're on a device that's running a version of Android lower than 5.0*, the posts will be using LAYER_TYPE_NONE which doesn't try to generate a bitmap of the view, and bam now posts are readable on devices with lower end GPUs. I'm psyched. I'm so sorry it took this long to fix it (and so sorry about the lack of communication, this bug has been driving me crazy and I didn't want to post until I knew exactly what was happening).


* We're currently doing the test off 5.0 because I suspect this issue only happens on WebKit powered WebViews (5.0 switched over to a Chromium powered WebView) -- If it keeps happening on 5.0 or above I'll modify that condition to be something else. Sadly you can't just say "If this device has a GPU with a small buffer", but "if this device has a high res screen" is a good alternative test we might switch over too.

Excuse my language, but:

enter image description here

When hotfixing a similar bug caused this to show up for more users, it came me as a great hint to what was causing it. Basically, we were trying to hardware accelerate all of our views and some GPUs just don't have big enough storage to handle how hilariously complex the WebViews we use for displaying posts are. Due to my ignorance, I had tried to fix this by setting the views to LAYER_TYPE_SOFTWARE which, you know, kind of sounds like the opposite of LAYER_TYPE_HARDWARE, but it turns out that they both use bitmap buffers and sometimes we still go over that limit!

So long story short, starting from version 1.0.59 (coming out sometime tomorrow, some other minor bugs I want to fix before that release) we finally have this issue fixed. If you're on a device that's running a version of Android lower than 5.0*, the posts will be using LAYER_TYPE_NONE which doesn't try to generate a bitmap of the view, and bam now posts are readable on devices with lower end GPUs. I'm psyched. I'm so sorry it took this long to fix it (and so sorry about the lack of communication, this bug has been driving me crazy and I didn't want to post until I knew exactly what was happening).


* We're currently doing the test off 5.0 because I suspect this issue only happens on WebKit powered WebViews (5.0 switched over to a Chromium powered WebView) -- If it keeps happening on 5.0 or above I'll modify that condition to be something else. Sadly you can't just say "If this device has a GPU with a small buffer", but "if this device has a high res screen" is a good alternative test we might switch over too.

2 added 3 characters in body
source | link

Excuse my language, but:

enter image description here

When hotfixing a similar bug caused this to show up for more users, it came me as a great hint to what was causing it. Basically, we were trying to hardware accelerate all of our views and some GPUs just don't have big enough storage to handle how hilariously complex the WebViews we use for displaying posts are. Due to my ignorance, I had tried to fix this by setting the views to LAYER_TYPE_SOFTWARE which, you know, kind of sounds like the opposite of LAYER_TYPE_HARDWARE, but it turns out that they both use bitmap buffers and sometimes we still go over that limit!

So long story short, starting from version 0.1.59 (coming out sometime tomorrow, some other minor bugs I want to fix before that release) we finally have this issue fixed. If you're on a device that's running a version of Android lower than 5.0*, the posts will be using LAYER_TYPE_NONE which doesn't try to generate a bitmap of the view, and bam now posts are readable on devices with lower end GPUs. I'm psyched. I'm so sorry it took this long to fix it (and so sorry about the lack of communication, this bug has been driving me crazy and I didn't want to post until I knew exactly what was happening).


* We're currently doing the test off 5.0 because I suspect this issue only happens on WebKit powered WebViews (5.0 switched over to a Chromium powered WebView) -- If it keeps happening on 5.0 or above I'll modify that condition to be something else. Sadly you can't just say "If this device has a GPU with a small buffer", but "if this device has a high res screen" is a good alternative test we might switch over too.

Excuse my language, but:

enter image description here

When hotfixing a similar bug caused this to show up for more users, it came me a great hint to what was causing it. Basically, we were trying to hardware accelerate all of our views and some GPUs just don't have big enough storage to handle how hilariously complex the WebViews we use for displaying posts are. Due to my ignorance, I had tried to fix this by setting the views to LAYER_TYPE_SOFTWARE which, you know, kind of sounds like the opposite of LAYER_TYPE_HARDWARE, but it turns out that they both use bitmap buffers and sometimes we still go over that limit!

So long story short, starting from version 0.1.59 (coming out sometime tomorrow, some other minor bugs I want to fix before that release) we finally have this issue fixed. If you're on a device that's running a version of Android lower than 5.0*, the posts will be using LAYER_TYPE_NONE which doesn't try to generate a bitmap of the view, and bam now posts are readable on devices with lower end GPUs. I'm psyched. I'm so sorry it took this long to fix it (and so sorry about the lack of communication, this bug has been driving me crazy and I didn't want to post until I knew exactly what was happening).


* We're currently doing the test off 5.0 because I suspect this issue only happens on WebKit powered WebViews (5.0 switched over to a Chromium powered WebView) -- If it keeps happening on 5.0 or above I'll modify that condition to be something else. Sadly you can't just say "If this device has a GPU with a small buffer", but "if this device has a high res screen" is a good alternative test we might switch over too.

Excuse my language, but:

enter image description here

When hotfixing a similar bug caused this to show up for more users, it came me as a great hint to what was causing it. Basically, we were trying to hardware accelerate all of our views and some GPUs just don't have big enough storage to handle how hilariously complex the WebViews we use for displaying posts are. Due to my ignorance, I had tried to fix this by setting the views to LAYER_TYPE_SOFTWARE which, you know, kind of sounds like the opposite of LAYER_TYPE_HARDWARE, but it turns out that they both use bitmap buffers and sometimes we still go over that limit!

So long story short, starting from version 0.1.59 (coming out sometime tomorrow, some other minor bugs I want to fix before that release) we finally have this issue fixed. If you're on a device that's running a version of Android lower than 5.0*, the posts will be using LAYER_TYPE_NONE which doesn't try to generate a bitmap of the view, and bam now posts are readable on devices with lower end GPUs. I'm psyched. I'm so sorry it took this long to fix it (and so sorry about the lack of communication, this bug has been driving me crazy and I didn't want to post until I knew exactly what was happening).


* We're currently doing the test off 5.0 because I suspect this issue only happens on WebKit powered WebViews (5.0 switched over to a Chromium powered WebView) -- If it keeps happening on 5.0 or above I'll modify that condition to be something else. Sadly you can't just say "If this device has a GPU with a small buffer", but "if this device has a high res screen" is a good alternative test we might switch over too.

    Bounty Ended with 50 reputation awarded by ShaWiz
1
source | link