aws-amplify / aws-amplify/amplify-hosting

Amplify hangs because it downloads >200MB of log files in the browser on page load

Open
#2,292 3 comments 1 reaction 0 assignees View on GitHub
bug
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-console/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-console/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-console/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

d21nzwkm439ia

### Region

eu-west-1

### Amplify Console feature

Not applicable

### Describe the bug

When visiting any page (even the environment variables) of the amplify console, it starts downloading over 200MB of logs. This crashes the browser

### Expected behavior

- It should not download logs it doesn't have to
- When downloading a log, it would be better to only download what is currently on the screen
- Not sure how we got to >35MB per log in the first place (we don't log millions of lines as far as I know)

Basically I have around 5 seconds now to do anything in the console before it starts hanging and eventually crashes, also the build output cannot be viewed ever for any pipeline

Screenshot:

![image](https://user-images.githubusercontent.com/4309740/135599478-3c2f8058-9320-40e6-8761-f4a0abd41bae.png)

### Reproduction steps

Visit any page in the console, but this behaviour happens only quite recently. Maybe because our app contains many builds now (>1000, but <10 open review apps) and some automated build branches have >600 deploys (like staging and production).

### Build Settings

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by visiting any Amplify Console page, especially the environment variables page, for an app with many builds, and inspect browser network activity for log downloads. Trace the request that loads logs and verify that pages no longer fetch hundreds of megabytes while build output remains viewable.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.