Issue metadata
Sign in to add a comment
|
Silent tab crash in my in-development application
Reported by
wanderin...@sfr.fr,
Oct 19 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/604.1.38 (KHTML, like Gecko) Version/11.0 Safari/604.1.38 Steps to reproduce the problem: 1. Load http://wanderingcoder.net/projects/JPS-dev/crBugDemonstrator1/ 2. Put attached "base-neutered' as the original file 3. Put attached "sw-127-neutered.bps" as the BPS format patch What is the expected behavior? Processing completes, in that a download area appears with an anchor to the URL for the completed blob. What went wrong? Towards the end of processing, the process for the tab silently crashes. I do not get even a sad tab. Did this work before? N/A Does this work in other browsers? No For the same processing, Firefox completes but the actual download fails (resource not found). Safari (of all browsers!) handles this as expected. Chrome version: 62.0.3202.62 (Build officiel) (64 bits) Channel: stable OS Version: OS X 10.11.6 Flash Version: 27.0.0.170 I admit my processing may be a bit complicated (yes, it does create thousands of blobs), I have some ideas on optimizations but I don't even know which to start with since I don't know what overloads the tab in the first place (hard to even get "in case I die on the next command" message out of there when the whole tab crashes: dev tools simply get disconnected and are of no help). For what it's worth, in the process manager the tab did not seem to have runaway memory usage before crashing. Sorry I can't reduce this more, but the issue is in all likelihood related to the complexity of the processing.
,
Oct 23 2017
Unable to reproduce the issue on the reported chrome version stable 62.0.3202.62 and on the latest canary 64.0.3247.0 using Windows10, Ubuntu 14.04 and Mac 10.12.6 with the steps mentioned in comment#0. Attaching the screenshot of the same. We observed no crash rather it's showing "Patched". @Reporter: Could you please check the issue in a new profile. Providing crash ID would help us in triaging the issue in a better way. Thanks!
,
Oct 23 2017
Indeed, checking on my side with Chrome Version 62.0.3202.62 (Build officiel) (64 bits) Channel stable on Windows (7 pro SP 1), I do not get the issue. Very strange. How would I get the crash ID? The crashed tab is empty, not even a sad tab, I have no pointer on where the information to report would be.
,
Oct 23 2017
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 23 2017
However, back at home I am checking on Max OS X Sierra (10.12.6 (16G29)) (a second Mac that is more recent but I haven't updated to High Sierra), and I do reproduce (Chrome Version 62.0.3202.62 (Build officiel) (64 bits)). I followed the instructions at http://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug , but even after 1. enabling the setting 2. reproducing the issue 3. checking chrome://crashes/ I don't get any entry! I also checked ~/Library/Logs/, and there is no CrashReporter at all (so no crash report); there is a "DiagnosticReports" folder but it is empty. This is really, really, really strange…
,
Oct 25 2017
Additional data point: on Chrome on Linux*, processing completes in that the download area appears, but clicking on it does nothing, even though the blob: URL is there. That one platform may be the most problematic, as some of my users are on Chromebooks and I have to assume it won't work there either… *I did not remember to note the version number, though it was a freshly installed google-chrome-stable package from the Ubuntu 14.04 public repositories.
,
Oct 26 2017
Able to reproduce the issue on Mac 10.12.6 using chrome reported version #62.0.3202.62 and latest canary #64.0.3249.0. Issue is not seen in OS-Win and OS-Linux. Bisect Information: ===================== Good build: 51.0.2694.0 Revision(383878) Bad Build : 51.0.2695.0 Revision(384157) Change Log URL: https://chromium.googlesource.com/chromium/src/+log/fe1e90eeacdc473325519df9c556d1cffa5db3a0..d88171b10e74122f7ac1410370dd056314ffc25f Unable to find any possible suspect from the above change log. Hence, marking it as untriaged and requesting someone from Blink>FileAPI team to help us in assigning it to the right owner. Thanks...!!
,
Oct 27 2017
In the above bisect, https://chromium.googlesource.com/chromium/src/+/1fb98480c61c563587cbb01de87cfad180fec942 shows up ("async bob construction") dmurph@ - can you take a look?
,
Jun 15 2018
,
Jun 15 2018
,
Jan 3
adding pwnall@ as this is P1, and unfortunately really old. Might not repro anymore. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Oct 20 2017