Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome extension crashes Edge (chromium) when trying to fill in sign up #763

Open
surgicalcoder opened this issue Dec 25, 2024 · 5 comments

Comments

@surgicalcoder
Copy link

Describe the Bug

Installed the latest version of the chrome extension (1.2.3) onto Edge version Version 131.0.2903.112 (Official build) (64-bit) and when trying to fill in the URL for my instance of hoarder, it crashes the entire browser, forcing a restart

Steps to Reproduce

  1. Install Edge
  2. Install Hoarder plugin
  3. Click on the plugin to start sign up
  4. Click on the text box to enter url of instance, try to type in

Expected Behaviour

Not to crash the browser

Screenshots or Additional Context

No response

Device Details

Edge 131.0.2903.112 on Windows 11 23H2 (22631.4602)

Exact Hoarder Version

v0.20.0

@MohamedBassem
Copy link
Collaborator

Wow. Crashing the entire browser smells like an edge problem rather than a hoarder problem. I'd be super surprised if extensions are allowed to crash entire browsers that way.

@surgicalcoder
Copy link
Author

Yeah I was really surprised too, I've tried disabling all extensions I have on here, no luck.

Interestingly though it only happens on Edge release version, not Dev or Canary.

It's not being reported as an app crash in terms of being picked up by WER. Maybe I was too hasty in opening this bug...

@solemgar
Copy link

solemgar commented Dec 28, 2024

Experiencing the same behavior. This time on MacOS so no OS dependent. It is possible to set the server address via config file?

@kamtschatka
Copy link
Contributor

I can not reproduce this issue and I honestly don't see how hoarder would be causing this.
I would rather assume there is an issue in Edge/Chromium and it should be reported in their bugtracker instead.

@solemgar
Copy link

@kamtschatka thanks for the quick reply. Are you trying on a edge browser release ?
Is it possible to set the server address other way so we can test if the extension still works?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants