Segfault on firefox 45.0.2 about certainmangareader

[Keats]

@Saishy can you reproduce this?

[Saishy]

sorry for the delay, can you give me your manga list? you can export them if you update to beta.

[Keats]

Here's the export https://gist.github.com/Keats/cced29bf180b7631cdef2a8cecbe86f3

[Keats]

Updated to firefox 46 and the problem persists, let me know if i can help

[Keats]

@Saishy any update?

[Saishy]

Sorry, it's really hard to get a time for debugging, especially a side project :c

[Keats]

So i've emptied the list quite a bit, it seems the updater doesn't handle errors, ie if the manga is deleted on batoto, it will get stuck at that one. I guess the segfault was due to the same kind of issue

[Saishy]

I'm tackling the issue now, sorry for the delay.

[Keats]

Here's the cleaned down list https://gist.github.com/Keats/6829a009b6be682967213437213d564a

[Saishy]

A quick question, has you tried to log-in into bato.to before updating?

I think the culprit might be Ballroom e Youkoso, it's not possible to have access to the first chapter if you are not logged in. But I see no reason for it to give a segfault, and actually while updating your own list in my computer it doesn't give a segfault, only stops updating.

[Keats]

I just signed in and it managed to get further in the update but now segfaults again, the last it was able to update is Fairy Tail from that list

[Saishy]

Edit: Could you check if Dungeon Meshi is the problem?

[Keats]

Nope, removed it and it still crashes

[Keats]

Can you a debug option that gives a notification before updating a manga and space them by a few seconds?
It would makes finding the culprit very fast, it's something after the letter B since those can update ok

[Saishy]

segfault_cmr.txt

I could get the error with this config, but it wasn't giving the error at all runs.

[Keats]

It seems to happen to random mangas actually. Do you have any idea why it happens?

[Saishy]

I have absolutely no idea, debugging it has been a pain since firefox doesn't have support for break on error.

Still working on it.

[Keats]

I might have a try at porting the extension to webextensions, those seem easier to maintain