New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 596713 link

Starred by 1 user
Status: WontFix
Owner:
vapier@chromium.org
Closed: Mar 2016
Cc:
llozano@chromium.org
vapier@chromium.org
jorgelo@chromium.org
█ earthdok@chromium.org
est...@chromium.org
█ glider@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

__libc_start_main-1ccaf39d

Project Member Reported by keta...@chromium.org, Mar 21 2016 

Chrome OS version: 7978.18.0

Top crasher in M50 affecting Samus only - 22 crashes reported so far all new and not seen in the last 49 Beta or the last M50 Beta. 

Sample Crash report ID: 02b9f2e800000000

Stable Signature__libc_start_main-1ccaf39dedit bugs&comments
Report TimeSat, 19 Mar 2016 12:17:51 GMT
Client IDADBDE0466E57435A967BDC4703F654BE
Filesminidump
Thread 0 CRASHED [SIGSEGV @ 0x00000000 ] MAGIC SIGNATURE THREAD
0x0040af3b	(wasm-as + 0x0000af3b )	
0x00007f6829815fb5	(libc-2.19.so -libc-start.c:292 )	__libc_start_main
0x0040ba3c	(wasm-as + 0x0000ba3c )

Might be related to crbug.com/364436. Assigning to vapier@. Please feel free to reassign to the right owner.

Comment 1 by vapier@chromium.org, Mar 21 2016

Labels: -Restrict-View-Google
Status: WontFix (was: Assigned)
this is a random /usr/local/bin/wasm-as file, so the only way that happened is this is a dev/test device running random code.  considering the nature of the program (appears to be WebAssembly related), i wouldn't be surprised if it employs weird memory tricks resulting in bad crash reports.

unless you locate the person running this code, i'd say just ignore all reports related to /usr/local/bin/wasm-as.

Comment 2 by keta...@chromium.org, Mar 22 2016 

ok. Thanks vapier@.
►

Sign in to add a comment