Having bitbucket pipeline log page opened in a tab makes the tab crash with "aw snap"
Reported by
martin.v...@gmail.com,
Apr 11 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/65.0.3325.181 Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Run a build and open a bitbucket pipeline 2. Wait 1-4 minutes What is the expected behavior? The tab should not crash What went wrong? The "Aw snap" is shown Crashed report ID: How much crashed? Just one tab Is it a problem with a plugin? No Did this work before? N/A Chrome version: 65.0.3325.181 Channel: stable OS Version: Chromium on Ubuntu 18.04 Flash Version: no flash I'm running Chromium from snap: snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: canonical contact: https://forum.snapcraft.io/ license: unknown description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: stable refreshed: 2018-04-03T17:21:31+03:00 installed: 65.0.3325.181 (274) 144MB - channels: stable: 65.0.3325.181 (274) 144MB - candidate: 65.0.3325.181 (274) 144MB - beta: ↑ edge: ↑
,
Apr 14 2018
Sorry, I'm not sure I can - Ubuntu Chromium build has crash reports disabled. Quoting my Chromium: Crash reporting is disabled. Crash reporting is not available in Chromium. However, I've reported the crash into the launchpad as well: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1763765
,
Apr 14 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 16 2018
Seems it is out of scope from TE end (as it build relates issue), adding TE-NeedsTraige-help label to move this out of our triaging bucket. Could someone from dev team please take a look into this issue. Thanks..!
,
Apr 26 2018
Can you debug it as per: https://wiki.ubuntu.com/Chromium/Debugging And provide a stack trace?
,
Apr 27 2018
I will try, thank you. However meanwhile this stack-trace may help? ``` StacktraceTop: v8::base::OS::Abort() () at ../../v8/src/base/platform/platform-posix.cc:372 FatalProcessOutOfMemory () at ../../v8/src/api.cc:397 Init () at ../../v8/src/isolate.cc:2950 Initialize () at ../../v8/src/snapshot/snapshot-common.cc:52 IsolateNewImpl () at ../../v8/src/api.cc:8393 ```
,
Apr 27 2018
Pasting the follow-up discussion here: Q: Is bitbucket pipeline log known to be memory-hungry? A: Yes, the log may get quite long, in my case it is a 8,5 megabytes long txt file. Generally bitbucket pipeline runs a (maven)-based build after every git commit, and you can watch the particular pipeline web page to watch the log unwind as the build progresses. The thing is, when you open a finished pipeline, Chromium has no trouble displaying page with a 8,5MB log. However, when you start the pipeline and watch the log progress from zero, Chromium will eventually crash well before the log hits, say, 1MB. So I'd assume it's the refreshing of that particular page which brings Chromium down.
,
Jun 8 2018
This sounds like it is a javascript memory leak in the buildbucket code. You should try to take memory snapshots in the developer tools and see if any of your JS code is leaking memory.
,
Jun 28 2018
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jmukthavaram@chromium.org
, Apr 12 2018Labels: Needs-Feedback Needs-Triage-M65