Crashes! behind system proxy

[CatchMeIUC]

I'm using U 22.04 and a VPN app to go out . My system proxy is 127.0.0.1:. I have to use the app + system proxy pair for Internet.

Every time I click Browse, the app crashed with error "Segmentation fault (core dumped)"

Please tell me the solution. Thanks!

[gapplef]

I have the same problem.

[elenio72]

Same problem here.

[mjakeman]

This will be a problem somewhere in the networking code. Unfortunately as I don't have any kind of system proxy to connect to, I'm not able to debug this myself anytime soon.

If someone technically inclined would like to help, the first step would be to generate a backtrace to see where the crash is occurring. Maybe this article can help: https://blogs.gnome.org/mcatanzaro/2021/09/18/creating-quality-backtraces-for-crash-reports/

I'll mark this as "Help Wanted" for now.

[elenio72]

In order to help, I attach two files with backtraces.
ex-manager-crash1.log
ex-manager-crash2.log

[mjakeman]

Hi @elenio72, could you attach the output of the bt (backtrace) command when using gdb?

The attached backtraces do not include function signatures so I can't tell where the crash occurred, other than that it did occur somewhere in extension-manager.

[ZCShou]

I have the same problem. When system's proxy is enabled and switching the browse tab, it would crash.

[elenio72]

Hi @elenio72, could you attach the output of the bt (backtrace) command when using gdb?

The attached backtraces do not include function signatures so I can't tell where the crash occurred, other than that it did occur somewhere in extension-manager.

(gdb) bt
#0 0x00007f1e0990440b in ?? ()
#1 0x00007f1e099144f3 in ?? ()
#2 0x000009c9b0e0f15b in ?? ()
#3 0x0000000000000000 in ?? ()

[mjakeman]

(gdb) bt
#0 0x00007f1e0990440b in ?? ()
#1 0x00007f1e099144f3 in ?? ()
#2 0x000009c9b0e0f15b in ?? ()
#3 0x0000000000000000 in ?? ()

Ah, that means debug symbols are not loaded. I won't be able to narrow it down using that. I'll try get access to a proxy from somewhere, let's aim to have this fixed for the (upcoming) 0.4 release.

[mjakeman]

I've now pushed Extension Manager 0.4 to Flathub Beta.

It has a built in crash monitor which will generate a report after crashing. Since I don't have access to a proxy, I would appreciate if someone could run the new version and upload the generated backtrace here.

Thanks!

---

You can install 0.4 as follows:

# Add flathub-beta
flatpak remote-add --if-not-exists flathub-beta https://flathub.org/beta-repo/flathub-beta.flatpakrepo

# Install Extension Manager
flatpak install flathub-beta com.mattjakeman.ExtensionManager

It is a good idea to remove flathub-beta and uninstall extension-manager afterwards as it will not be automatically updated when the final release comes out.

The crash window looks like this:

[elenio72]

With 0.4 version the problem is resolved. Now I can browse the extensions available correctly behind enterprise network proxy.
Thanks!

[mjakeman]

@elenio72 Great to hear! I'll close this issue then, if any other (possibly related) problems pop-up, please open a new issue :)