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.

Sign up for GitHub

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

Jump to bottom

Canvas constructor crashes with bad arguments #70

Closed
FlutterIssues opened this issue Nov 9, 2015 · 3 comments
Closed

Canvas constructor crashes with bad arguments #70

FlutterIssues opened this issue Nov 9, 2015 · 3 comments
Labels
c: crash Stack traces logged to the console engine flutter/engine repository. See also e: labels. waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds

Comments

@FlutterIssues
Copy link

Issue by Hixie
Thursday Jul 16, 2015 at 22:25 GMT
Originally opened as https://github.com/flutter/engine/issues/23

From @Hixie on July 15, 2015 21:0

My reading of the Canvas constructor is that it'll crash if you call it with a null first argument.
The comment also explicitly says that it'll crash if you call it with a PictureRecorder in the wrong state.

The APIs the C++ expose to the Dart code should never be able to crash the app.

Copied from original issue: domokit/mojo#326
@FlutterIssues FlutterIssues added bug c: crash Stack traces logged to the console engine flutter/engine repository. See also e: labels. labels Nov 9, 2015
@Hixie Hixie removed the ⚠ bug label Dec 12, 2015
@Hixie Hixie mentioned this issue Dec 14, 2015
Closed
@Hixie Hixie modified the milestone: Blue Sky Dec 16, 2015
@jason-simmons jason-simmons mentioned this issue Jul 21, 2016
Closed
@sethladd sethladd added the waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds label Sep 14, 2016
@sethladd
Copy link
Contributor

Is this still an issue?

@Hixie
Copy link
Contributor

Hixie commented Sep 14, 2016

The first case listed here is fixed. The second is also filed as #2531, so I'll close this one.

@Hixie Hixie closed this as completed Sep 14, 2016
@gavindoughtie gavindoughtie mentioned this issue Dec 2, 2016
Closed
@ppolasek ppolasek mentioned this issue Feb 8, 2017
Closed
@skybrian skybrian mentioned this issue Feb 16, 2017
Closed
@Reagankm Reagankm mentioned this issue Feb 24, 2017
Closed
@collinjackson collinjackson mentioned this issue May 19, 2017
Closed
@jamesgopinath jamesgopinath mentioned this issue Aug 4, 2017
Closed
@apwilson apwilson mentioned this issue Aug 10, 2017
Closed
@gavindoughtie gavindoughtie mentioned this issue Sep 25, 2017
Closed
@arnold-nonstop arnold-nonstop mentioned this issue Sep 29, 2017
Closed
@amirh amirh mentioned this issue Oct 9, 2017
Closed
@PlanovskyJus PlanovskyJus mentioned this issue Nov 3, 2017
Closed
@steele232 steele232 mentioned this issue Nov 9, 2017
Closed
@Hixie Hixie mentioned this issue Dec 11, 2017
Closed
@silverAndroid silverAndroid mentioned this issue Dec 14, 2017
Closed
@Monotoba Monotoba mentioned this issue Dec 28, 2017
Closed
Closed
@ybmeng ybmeng mentioned this issue Feb 28, 2018
Closed
@gorjan-mishevski gorjan-mishevski mentioned this issue Mar 6, 2018
Open
@Niroop4444 Niroop4444 mentioned this issue Oct 1, 2020
Closed
@JeetBhattachariya JeetBhattachariya mentioned this issue Oct 8, 2020
Closed
This was referenced Oct 16, 2020
Closed
Closed
Closed
@lv823063712 lv823063712 mentioned this issue Oct 19, 2020
Closed
@right7ctrl right7ctrl mentioned this issue Oct 24, 2020
Closed
@Jiangshan2015 Jiangshan2015 mentioned this issue Oct 30, 2020
Closed
@hasanworks hasanworks mentioned this issue Oct 30, 2020
Closed
@Tony-Akani Tony-Akani mentioned this issue Nov 1, 2020
Closed
@kw2019ltd kw2019ltd mentioned this issue Nov 16, 2020
Closed
@issantech issantech mentioned this issue Nov 23, 2020
Closed
This was referenced Nov 28, 2020
Closed
Closed
This was referenced Dec 11, 2020
Closed
Closed
@sureace sureace mentioned this issue Jan 13, 2021
Closed
@staminna staminna mentioned this issue Jan 22, 2021
Closed
@yannainghtun-mk yannainghtun-mk mentioned this issue Jan 26, 2021
Closed
@1005274291 1005274291 mentioned this issue Jan 26, 2021
Closed
@praneethpj praneethpj mentioned this issue Jan 29, 2021
Closed
@sravanpabolu sravanpabolu mentioned this issue Feb 11, 2021
Closed
@lianchengtong lianchengtong mentioned this issue Feb 13, 2021
Closed
@Marko1994 Marko1994 mentioned this issue Mar 4, 2021
Closed
@bladeofgod bladeofgod mentioned this issue Apr 14, 2021
Open
@SlowGen SlowGen mentioned this issue May 27, 2021
Closed
@akashgk akashgk mentioned this issue Jun 18, 2021
Closed
@94wogus 94wogus mentioned this issue Jul 3, 2021
Open
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
c: crash Stack traces logged to the console engine flutter/engine repository. See also e: labels. waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sethladd @Hixie @FlutterIssues