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.

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

Dartium crashed randomly during debug #19927

Closed
DartBot opened this issue Jul 9, 2014 · 11 comments
Closed

Dartium crashed randomly during debug #19927

DartBot opened this issue Jul 9, 2014 · 11 comments
Labels
needs-info We need additional information from the issue author (auto-closed after 14 days if no response) P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@DartBot
Copy link

DartBot commented Jul 9, 2014

This issue was originally filed by kunzhao77...@gmail.com


What steps will reproduce the problem?

  1. Run dart project from DartEditor
    2.
    3.

What is the expected output? What do you see instead?
Dart project up and running. I experienced a random crash. In DartEditor output, it shows <debug target crashed> without any detailed information

What version of the product are you using? On what operating system?
Dart SDK version 1.6.0-dev.1.2 on Mac OS X

Please provide any additional information below.
My project is drawing on SVG canvas. I'm suspecting that there might be some timing issue or race condition when adding a new SVG element into the canvas, because it won't crash if I step through the code where adding new element into the canvas, if I let it run, sometimes it crashes.

I don't see the crash prior version 1.6.0

@anders-sandholm
Copy link
Contributor

Assigning prio high given that we're crashing. feel free to change prio if I'm off.

There is no repro so not sure if we can fix it for 1.6. Again, feel free to re-arrange as you see fit.


Added this to the 1.6 milestone.
Removed Priority-Unassigned label.
Added Priority-High, Area-Editor, Triaged labels.

@clayberg
Copy link

Removed Area-Editor label.
Added Area-Dartium, Duplicate labels.
Marked as being merged into #19853.

@dgrove
Copy link
Contributor

dgrove commented Jul 10, 2014

@kunzhao77, can you please either provide repro instructions or follow these instructions and provide a stack trace:

https://code.google.com/p/dart/wiki/DebuggingDartium


Added NeedsInfo label.
Marked as being merged into #.

@DartBot
Copy link
Author

DartBot commented Jul 10, 2014

This comment was originally written by @filiph


Seems like the same issue I hit with https://code.google.com/p/dart/issues/detail?id=19853

@DartBot
Copy link
Author

DartBot commented Jul 11, 2014

This comment was originally written by kunz...@gmail.com


I am on Mac, I can't get crash dump. In the link, it said only tested in
linux.
Is there any instruction about how to make it work in Mac?

Reading symbols from
/Users/kzhao/repo/dart-repo/dart/client/tests/dartium/Chromium.app/Contents/MacOS/Chromium...

warning:
`/Volumes/data/b/build/slave/dartium-mac-debug-be/build/src/out/Debug/obj/chrome/app/chrome_initial.chrome_exe_main_mac.o':
can't open to read symbols: No such file or directory.

warning:
`/Volumes/data/b/build/slave/dartium-mac-debug-be/build/src/out/Debug/obj/content/public/common/chrome_initial.content_switches.o':
can't open to read symbols: No such file or directory.

(no debugging symbols found)...done.

(gdb) r

Starting program:
/Users/kzhao/repo/dart-repo/dart/client/tests/dartium/Chromium.app/Contents/MacOS/Chromium
--single-process --disable-hang-monitor --no-sandbox
http://localhost:8080/adl.html

Unable to find Mach task port for process-id 67094: (os/kern) failure (0x5).

 (please check gdb is codesigned - see taskgated(8))

(gdb)

@a-siva
Copy link
Contributor

a-siva commented Jul 11, 2014

Would it be possible to provide us a part of your project that does the SVG canvas drawing so that we can try and reproduce the problem here.

@a-siva
Copy link
Contributor

a-siva commented Jul 11, 2014

Added Dartium-Crasher label.

@DartBot
Copy link
Author

DartBot commented Jul 11, 2014

This comment was originally written by kunzha...@gmail.com


I will try if I can reproduce the crash in a simpler project.

@sethladd
Copy link
Contributor

Once we get a repro we'll bump back to High Pri.


Removed this from the 1.6 milestone.
Removed Priority-High label.
Added Priority-Medium label.

@DartBot
Copy link
Author

DartBot commented Jul 25, 2014

This comment was originally written by kunz...@gmail.com


I uploaded my project trough gmail on July 13, but it didn't show up here. I'm attaching it here again.

A simplified project is attached. To reproduce the crash:

  1. Set Preferences->Ran and Debug->Break on exception to None. (This is new bug that break on uncaught exception doesn't work).
  2. left click on the canvas and drag while holding the left mouse, a blue rectangle will show up.
  3. cover the two '0' with the blue rectangle then release left mouse button to select the two blocks.
  4. Once the two block selected, their border will change to orange.
  5. click ctrl+g key

Dartium crashed. The crash does not happen every time. If it didn't crash, just stop the project and repeat step 2~5.


Attachment:
adl_lib.zip (47.88 KB)

@DartBot
Copy link
Author

DartBot commented Jul 25, 2014

This comment was originally written by kunzhao7...@gmail.com


part 2.

dart_client project uses adl_lib.


Attachment:
dart_client.zip (93.61 KB)

@DartBot DartBot added Type-Defect needs-info We need additional information from the issue author (auto-closed after 14 days if no response) labels Jul 25, 2014
@kevmoo kevmoo added P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed Priority-Medium labels Mar 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-info We need additional information from the issue author (auto-closed after 14 days if no response) P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

8 participants