Former Member
inherit
guest@proboards.com
218958
0
May 4, 2024 6:12:15 GMT -8
Former Member
0
January 1970
Former Member
|
Post by Former Member on Feb 23, 2015 12:22:55 GMT -8
Just checking in, A few members who reported NOT having the issue previously are not reporting it as occurring for them. They did not update their iOS or change anything on their end.
|
|
inherit
218076
0
May 9, 2017 6:59:00 GMT -8
nariadreaming
877
January 2015
nariadreaming
|
Post by nariadreaming on Feb 23, 2015 12:30:56 GMT -8
As Theophania mentioned, we have additional users reporting this issue.
I know you have said this is high priority, but I hope that you will continue to escalate this situation and work diligently on it. Many of our users access our forums from their mobile devices, and I have honestly been disappointed in how slow the response from the tech team has been on this issue.
As we look to move our forums to a white-label service, I'm becoming concerned that perhaps the tech team at proboards/forums.net will not be able to adequately address major issues such as this in a timely manner.
|
|
#e61919
Support Manager
154778
0
1
May 3, 2024 16:11:00 GMT -8
Michael
19,550
May 2010
wiseowl
|
Post by Michael on Feb 23, 2015 13:24:14 GMT -8
Hi Everyone, We have been working diligently on this issue over the past few days. Unfortunately it isn't as simple as it would appear to address this sort of issue. As we've dug further and further into this issue and removing possible causes we've become aware that we might not be the only ones with this issue but results so far indicate that there is a memory leak issue of some sort. We have had a developer digging into this since the issues inception. We are continuing to explore every possibility as to the cause. It appears that others have discovered the same things that we have and have provided the same temporary but not definite resolutions to the issues. It is widely believed that there is mishandling on the part of Safari of some code that caused the issues. With the new information in this thread we hope to come closer to finding a solution. Thank you for your patience and understanding while we attempt to resolve this!
|
|
inherit
218076
0
May 9, 2017 6:59:00 GMT -8
nariadreaming
877
January 2015
nariadreaming
|
Post by nariadreaming on Feb 23, 2015 13:49:02 GMT -8
Hi Everyone, We have been working diligently on this issue over the past few days. Unfortunately it isn't as simple as it would appear to address this sort of issue. As we've dug further and further into this issue and removing possible causes we've become aware that we might not be the only ones with this issue but results so far indicate that there is a memory leak issue of some sort. We have had a developer digging into this since the issues inception. We are continuing to explore every possibility as to the cause. It appears that others have discovered the same things that we have and have provided the same temporary but not definite resolutions to the issues. It is widely believed that there is mishandling on the part of Safari of some code that caused the issues.With the new information in this thread we hope to come closer to finding a solution. Thank you for your patience and understanding while we attempt to resolve this! Users are also having this issue in Chrome on their iPads, so I doubt Safari is the issue
|
|
#e61919
Product Manager
12218
0
1
Mar 11, 2017 17:47:30 GMT -8
Matej
This is my status!
17,630
August 2003
wooper
|
Post by Matej on Feb 23, 2015 14:00:03 GMT -8
Hi Everyone, We have been working diligently on this issue over the past few days. Unfortunately it isn't as simple as it would appear to address this sort of issue. As we've dug further and further into this issue and removing possible causes we've become aware that we might not be the only ones with this issue but results so far indicate that there is a memory leak issue of some sort. We have had a developer digging into this since the issues inception. We are continuing to explore every possibility as to the cause. It appears that others have discovered the same things that we have and have provided the same temporary but not definite resolutions to the issues. It is widely believed that there is mishandling on the part of Safari of some code that caused the issues.With the new information in this thread we hope to come closer to finding a solution. Thank you for your patience and understanding while we attempt to resolve this! Users are also having this issue in Chrome on their iPads, so I doubt Safari is the issue Browsers on iOS are essentially forced to run the same WebKit engine as Safari, effectively making Chrome just Safari with a different interface. Sadly, this would still be a Safari related issue.
|
|
#e61919
Support Manager
154778
0
1
May 3, 2024 16:11:00 GMT -8
Michael
19,550
May 2010
wiseowl
|
Post by Michael on Feb 23, 2015 16:09:14 GMT -8
Hi Everyone, We have been working diligently on this issue over the past few days. Unfortunately it isn't as simple as it would appear to address this sort of issue. As we've dug further and further into this issue and removing possible causes we've become aware that we might not be the only ones with this issue but results so far indicate that there is a memory leak issue of some sort. We have had a developer digging into this since the issues inception. We are continuing to explore every possibility as to the cause. It appears that others have discovered the same things that we have and have provided the same temporary but not definite resolutions to the issues. It is widely believed that there is mishandling on the part of Safari of some code that caused the issues.With the new information in this thread we hope to come closer to finding a solution. Thank you for your patience and understanding while we attempt to resolve this! Users are also having this issue in Chrome on their iPads, so I doubt Safari is the issue I know Matej addressed this above but Apple has such a tight reign on the apps that are allowed on the app store that all other "alternative" browsers available are really just re-skinned versions of the stock Safari browser (to put it simply). No matter what browser you use on an Apple device, its basically exactly the same. Currently we're investigating the fact that it might be something unrelated to our code like an ad issue. Thank you for your continued patience!
|
|
#e61919
Product Manager
12218
0
1
Mar 11, 2017 17:47:30 GMT -8
Matej
This is my status!
17,630
August 2003
wooper
|
Post by Matej on Feb 23, 2015 16:48:37 GMT -8
Hi again!
We believe we have identified what is causing the memory issue and subsequent reloading on iOS.
The code is currently in testing and review before it gets pushed out to users.
Assuming everything goes well, the fix could be pushed live tomorrow morning.
|
|
inherit
218076
0
May 9, 2017 6:59:00 GMT -8
nariadreaming
877
January 2015
nariadreaming
|
Post by nariadreaming on Feb 24, 2015 9:25:18 GMT -8
Hi again! We believe we have identified what is causing the memory issue and subsequent reloading on iOS. The code is currently in testing and review before it gets pushed out to users. Assuming everything goes well, the fix could be pushed live tomorrow morning. Is there a status update?
|
|
#e61919
Support Manager
154778
0
1
May 3, 2024 16:11:00 GMT -8
Michael
19,550
May 2010
wiseowl
|
Post by Michael on Feb 24, 2015 9:33:41 GMT -8
Hi again! We believe we have identified what is causing the memory issue and subsequent reloading on iOS. The code is currently in testing and review before it gets pushed out to users. Assuming everything goes well, the fix could be pushed live tomorrow morning. Is there a status update? Well the ProBoards office just opened 32 minutes ago right now so...yes! We believe the issue has been resolved and pushed wide to all forums.
|
|
inherit
218076
0
May 9, 2017 6:59:00 GMT -8
nariadreaming
877
January 2015
nariadreaming
|
Post by nariadreaming on Feb 24, 2015 10:28:11 GMT -8
Is there a status update? Well the ProBoards office just opened 32 minutes ago right now so...yes! We believe the issue has been resolved and pushed wide to all forums. Thank you! And silly Pacific Time Zone. No rest for the weary Thanks again for your hard work
|
|
inherit
218742
0
Apr 30, 2016 13:30:49 GMT -8
adminsew
21
February 2015
adminsew
|
Post by adminsew on Feb 24, 2015 11:33:56 GMT -8
Well so far so good, as the originator of this thread I would like to thank all the Proboards support for their help, it is much appreiciated.
|
|
Former Member
inherit
guest@proboards.com
218958
0
May 4, 2024 6:12:15 GMT -8
Former Member
0
January 1970
Former Member
|
Post by Former Member on Feb 24, 2015 14:33:41 GMT -8
My users are currently responding that it's working properly for them now. Thank you so much! I'll update if anyone has any other issues, but it looks good.
|
|
inherit
169146
0
Apr 7, 2024 5:23:13 GMT -8
Forever Sunshine
Fingerprints don't fade from the lives we touch. Great love & great achievement involve great risk.
1,743
July 2011
foreversunshine
|
Post by Forever Sunshine on Feb 24, 2015 20:40:27 GMT -8
~*~ Thank you Michael, Matej and all the proboards staff who figured this out.
You are definitely the best of the best!
|
|
inherit
218742
0
Apr 30, 2016 13:30:49 GMT -8
adminsew
21
February 2015
adminsew
|
Post by adminsew on Feb 25, 2015 3:19:49 GMT -8
I've received feedback from my members that it all seems to be ok so far. Thanks again
|
|
inherit
169146
0
Apr 7, 2024 5:23:13 GMT -8
Forever Sunshine
Fingerprints don't fade from the lives we touch. Great love & great achievement involve great risk.
1,743
July 2011
foreversunshine
|
Post by Forever Sunshine on Feb 25, 2015 5:35:29 GMT -8
~*~ My members are doing a happy dance! All seems to be functioning normally for them! Woohoo!!!!!!!!!
|
|