Just ranting cause the devRant iOS app keeps crashing randomly when I open rants at times, after crash same rant opens fine.
A lot of “rant” on that sentence.

It happens all the time, worse on initial load or reopening the app, notifs screen can get broken (tabs stop responding) to be able to change the filter on those.

@dfox any fix for this in the future?

Also gifs upload as normal images from iOS, really tedious logging into the browser just to post a gif 😕

--
This seems to be a recurring issue in the logs.

Date/Time: 2020-05-10 08:39:12.2929 +1000
Launch Time: 2020-05-10 07:51:28.8173 +1000
OS Version: iPhone OS 13.4.1 (17E262)
Release Type: User
Baseband Version: 2.05.13
Report Version: 104

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x000000035caf5ff0
VM Region Info: 0x35caf5ff0 is not in any region. Bytes after previous region: 3165609969
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
MALLOC_NANO 0000000280000000-00000002a0000000 [512.0M] rw-/rwx SM=PRV
--->
UNUSED SPACE AT END

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [10762]
Triggered by Thread: 0

@C0D4 could post that log on the devRant github issue?
https://github.com/devRant/devRant/...

It happens all the time, since December.
Probably because of the new IOS 13 version.

@heyheni damn, github is not nice on mobile for this kind of thing.

@C0D4 thank you!

@dfox please help us, we iphone users are suffering way too long lol :D

@C0D4 segfault, oof
So turns out dfox is a mortal just like the rest of us

@RememberMe even "gods" make mistakes... check out the human race for example.

@RememberMe segfault? what kind of error is that? could you may explain that for me non code jedi? :D

Edit: nevermind, i was just too lazy. Found the wikipedia article. https://en.wikipedia.org/wiki/...

I almost used a bot for that 😅

@heyheni oh boy, there's a lot going on here, but in a very "sort of" manner:

The operating system gives each running program (a "process" in OS terminology) a region of memory that it is allowed to use, essentially a box that the process is supposed to confine itself to. When the process tries to access something outside that region, or "segment" as they were called back in the old days, the operating system says nah that's illegal and sends the process a signal called SIGSEGV...or as it's more commonly known, a segmentation fault or segfault. Since it tried to do something it wasn't supposed to do, it usually crashes.

This is usually caused by the program trying to access something by mistake, due to a coding error.

The real explanation involves something called virtual memory which is a fascinating topic if you want to read up on it, but the above mental image should do.

@RememberMe cool thank you very much!
And what's your take on how that could happen on devRant? Typo in the code? forgotten semicolon?

New version coming shortly that should hopefully fix all those issues!

@heyheni no idea. Segmentation faults are extremely general (literally just caused by trying to load data from an invalid memory block) so there are billions of reasons why it could happen. The more general the problem, the more things that could be the cause.

@heyheni in the sense of devRant and how it occurs only when trying to fetch new data, I would suspect there's a dropout or malformed data coming into the app and the app isn't handling the invalid data, so trying to find data that doesn't exist from the APi.

Probably (based on assumptions here) a fetch and use, rather then fetch, sanity check then use.

lol the app crashed five times while trying to look at your responses. But thankfully @dfox promised us a new app version. Thank you David 💛 for caring for us since four years!

@heyheni Most likely a null pointer resolution (a variable that was expected to have a value didn't have one).
They also produce segfaults in c(++).

New build went out last night - please let me know if that fixes some of these issues. Thanks!

@dfox I haven't manually updated an app in so long I almost forgot how.

Feels snappy, can't seem to break it loading notifs anymore 👍

@C0D4 awesome, thanks for checking!

@dfox hmm, tapping on a mention in the notifs screen triggered the app to crash 🤯

So close...

@highlight show some logs.

@C0D4 does it happen every time you go to a mention?

@dfox no.. just worked fine then.
But has happened on the last couple of notifs, not just mention, so might be related to loading the rant it's self.

@C0D4 does it happen on the same rant or consistently on specific rant(s)? Possibly longer ones with more comments?

@dfox Twice on this rant.

And the ++ from @wombat to this rant

https://devrant.com/rants/2531663/...

Closed the app when seeing what it was.

But the loading of the notifs screen works without issue (so far) so that's something 😉

@C0D4 would you say the frequency of tapping a notif and having it crash when loading the rant decreased with the latest build? Basically I identified a weird timing issue and I’m wondering if the delay I put in just needs to be increased some more.

@dfox early hours I think for that, but so far it does feel a lot less impactful.

Used to happen very often, this was the first since the update its had an issue.

@dfox if I keep opening a rant off the same notif enough times in a row it ends up crashing after a while, Hard to replicate and it seems somewhat random.

@dfox thank you for your efforts. Much appreciated. 😃
Sadly the problem persists for me. It crashes less after the update but still too often.

Taping on a notif in the notification tab leads to app closure 3 out of 10 times.
Scrolling too fast on a rant leads to a crash 4 out of 10 times.