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
Bus error from tools/testing/bin/macos/dart in r28631 #14343
Comments
Added OpSys-OSX label. |
It happened again. This time after 9:40 minutes. Added Triaged label. |
I ran the program under gdb and got: Program received signal EXC_BAD_ACCESS, Could not access memory. Thread 179 (process 69308): Thread 178 (process 69308): Thread 177 (process 69308): Thread 176 (process 69308): Thread 172 (process 69308): Thread 171 (process 69308): Thread 170 (process 69308): Thread 165 (process 69308): Thread 163 (process 69308): Thread 158 (process 69308): Thread 4 (process 69308): Thread 2 (process 69308): Thread 1 (process 69308): |
The actual crash happens in the Dart executable which is hosting the test runner right? Unfortunately that is a quite old version of Dart: Dart VM version: 0.1.2.0_r27044 (Tue Sep 3 04:46:44 2013) on "linux_ia32" It would be great to have a crash from a binary with symbols. Could it be out of memory? |
Removed Priority-Unassigned label. |
Removed Area-IO label. |
Added AssumedStale label. |
The last few lines were:
[43:01 | 85% | +10752 | - 558]2013-10-23 14:37:12.384 Warning: HttpServer: could not find file for request path: "/root_build/generated_tests/dart2js-drt/tests_html_safe_dom_test/_.png"
[43:34 | 86% | +10833 | - 558]Bus error: 10
I assume this is some kind of bug in dart:io, and I'll add more information if I see this problem again.
I'm filing this bug initially marked as "CannotReproduce", because I'm not sure I can reproduce the problem. It took 43 minutes to crash.
The text was updated successfully, but these errors were encountered: