[Bug] Clicking instance favicon causes crash

[deltatux]

Hi all,

Just encountered a bug, if you click on the instance favicon next to a username, it causes Mangane to crash, example:

Crash:

I was trying to see if the Akkoma syslogs would show me a reason for the crash but there doesn't seem to be a crash log that I can find. Let me know where I can pull the logs & I'll try to provide them to you.

Thanks!

[Cl0v1s]

Those crash screen a definately Mangane related ! Thanks for investigating :)

You made me discover this feature I did not know about 😆 However it works well on my instance. Do you have the same issues for all instances ? Or only for mastodon.nu ?

[deltatux]

Those crash screen a definately Mangane related ! Thanks for investigating :)

You made me discover this feature I did not know about laughing However it works well on my instance. Do you have the same issues for all instances ? Or only for mastodon.nu ?

Unfortunately it happens on all instances, I just so happened to use that mastodon.nu as an example. Everytime I press that favicon, regardless of instance, it causes Mangane to crash.

[Cl0v1s]

It will be hard for me to debug as I can't reproduce on bdx.town...

Can you show me the developer console on your browser ?

Le 30 décembre 2022 21:42:01 GMT+01:00, deltatux @.***> a écrit :

Those crash screen a definately Mangane related ! Thanks for investigating :)

You made me discover this feature I did not know about laughing However it works well on my instance. Do you have the same issues for all instances ? Or only for mastodon.nu ?

Unfortunately it happens on all instances, I just so happened to use that mastodon.nu as an example. Everytime I press that favicon, regardless of instance, it causes Mangane to crash.

-- Reply to this email directly or view it on GitHub: https://github.com/BDX-town/Mangane/issues/129#issuecomment-1368084219 You are receiving this because you commented.

Message ID: @.***>

[deltatux]

It will be hard for me to debug as I can't reproduce on bdx.town... Can you show me the developer console on your browser ? Le 30 décembre 2022 21:42:01 GMT+01:00, deltatux @.***> a écrit : …

Those crash screen a definately Mangane related ! Thanks for investigating :) > > You made me discover this feature I did not know about laughing However it works well on my instance. Do you have the same issues for all instances ? Or only for mastodon.nu ? Unfortunately it happens on all instances, I just so happened to use that mastodon.nu as an example. Everytime I press that favicon, regardless of instance, it causes Mangane to crash. -- Reply to this email directly or view it on GitHub: #129 (comment) You are receiving this because you commented. Message ID: @.***>

Hi @Cl0v1s,

Thanks for the reply, here's how it looks like when Mangane crashed:

Here's the console message details:

TypeError: Expected Array or collection object of values: true
    te list.tsx:1
    t announcements.ts:1
    t filters.ts:1
    t apps.ts:7
    Immutable 3
    toSimplePolicy config_db.ts:1
    Immutable 4
    toSimplePolicy config_db.ts:1
    I index.ts:18
    c index.js:67
    a index.js:30
    l index.js:82
    a index.js:30
    M index.ts:18
    l index.js:78
    a index.js:30
    p instance_info_panel.tsx:1
    Redux 2
    f instance_info_panel.tsx:1
    React 7
    unstable_runWithPriority scheduler.production.min.js:289
    React 5
    setState trending_statuses.ts:1
    l bundle.js:1
    promise callback*t/l< bundle.js:1
    componentDidMount bundle.js:1
    React 2
    unstable_runWithPriority scheduler.production.min.js:289
    React 4
    unstable_runWithPriority scheduler.production.min.js:289
    React 5
    setState trending_statuses.ts:1
    l bundle.js:1
    promise callback*t/l< bundle.js:1
    componentWillReceiveProps bundle.js:1
    React 8
    unstable_runWithPriority scheduler.production.min.js:289
    React 5
react-dom.production.min.js:4473:20
Firefox can’t establish a connection to the server at wss://tuxz.one/api/v1/streaming/?stream=public:remote&instance=tuxz.one. FormData.js:2
The connection to wss://tuxz.one/api/v1/streaming/?stream=public:remote&instance=tuxz.one was interrupted while the page was loading. FormData.js:2

Please let me know if you require additional info.

Thanks!

[deltatux]

It will be hard for me to debug as I can't reproduce on bdx.town... Can you show me the developer console on your browser ? Le 30 décembre 2022 21:42:01 GMT+01:00, deltatux @.***> a écrit : …

Those crash screen a definately Mangane related ! Thanks for investigating :) > > You made me discover this feature I did not know about laughing However it works well on my instance. Do you have the same issues for all instances ? Or only for mastodon.nu ? Unfortunately it happens on all instances, I just so happened to use that mastodon.nu as an example. Everytime I press that favicon, regardless of instance, it causes Mangane to crash. -- Reply to this email directly or view it on GitHub: #129 (comment) You are receiving this because you commented. Message ID: @.***>

Just thought to also do the same on a Chromium-based browser in case it was a Firefox specific bug but it isn't. Attached is the console output from the Brave browser.

Thanks! tuxz.one-1672552722313.log

[Cl0v1s]

Thanks for the details !

From the call stack I'd say it's related to some filters settings of yours. Do you have any content filters set ?

[deltatux]

Hi @Cl0v1s,

Sorry for the delayed reply, been a hectic couple of days on my end.

I did more testing, including removing all my filters but still running into the same issue. I also upgraded to the latest mangane release (nomadic hermit crab) and issue still reared its head..

I have attached 2 more console dumps as well, one is when I clicked the favicon from a status from journa.host and another from mediastodon.com.

Thanks!

firefox-console-dump-journahost.txt firefox-console-dump-mediastodon.txt

[Cl0v1s]

Ok good news ! I reproduced the issue on a fresh Akkoma install. Are you running Akkoma 3.5.0 ?

Thanks for your help !

[R3laxAti0n]

Hi,

Just to add that I had the same issue. Removing the exiftool filter from the Pleroma.upload configuration panel solved it for me.

Edit: It was solved yesterday, with no change in the configuration since then, the bug is up again today.

[deltatux]

Ok good news ! I reproduced the issue on a fresh Akkoma install. Are you running Akkoma 3.5.0 ?

Thanks for your help !

Hi @Cl0v1s,

Thanks for looking into this, yes I'm running Akkoma 3.5.

Thanks again!