openbullet / openbullet/OpenBullet2

HTTP Request source crashes openbullet2

Open
#1,076 0 comments 0 reactions 1 assignee View on GitHub

@openbullet is already working on this.

Since Jul 22, 2024.

area:frontend bug client:web
Dominant language
C#
Stars
2.4k
Forks
603
PR merge metrics
No merged PRs in 30d

Description

This issue respects the following points:
  • This is a bug, not a question or a configuration issue; Please visit our forum first to troubleshoot with volunteers, before creating a report. The links can be found here.
  • This issue is not already reported on GitHub (I've searched it).
  • I'm using an up to date version of OpenBullet2. We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
  • I agree to follow OpenBullet's Code of Conduct.
  • This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.
Description of the bug

When you make a http request and the source returns and it’s a huge it crashes open bullet 2 with out of memory.

When I asked for a remedy you told me to use this loli code and it worked

data.Logger.Enabled = false;
... your block here
data.Logger.Enabled = true;
Reproduction steps

HTTP Request…

What is the current bug behavior?

When the source returns it crashes the entire program

What is the expected correct behavior?

It shouldn’t crash

Version of the client

Openbullet2 new web design.

Type of client

Web client

Environment
- OS:windows 11
- Virtualization:
- Browser:Opera
OpenBullet2 logs

No response

Client / Browser logs

No response

Relevant screenshots or videos

No response

Relevant LoliCode if needed

No response

Additional information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.