Bug 410924 - massif crashes running jetstream2 benchmark with webkit
Summary: massif crashes running jetstream2 benchmark with webkit
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: massif (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Nicholas Nethercote
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-15 10:10 UTC by Paulo J. Matos
Modified: 2019-09-06 04:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
log from step 4 (18.16 KB, text/x-log)
2019-08-15 10:10 UTC, Paulo J. Matos
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paulo J. Matos 2019-08-15 10:10:02 UTC
Created attachment 122132 [details]
log from step 4

SUMMARY

Trying to run JetStream2 on the command line with JSC crashes massif. Happens with ubuntu valgrind 3.13 all the way to current tip of master branch in git.

STEPS TO REPRODUCE
1. Clone WebKit from git://git.webkit.org/WebKit.git and cd into it;
2. Build JSC only with Tools/Scripts/build-jsc --jsc-only --release
3. cd PerformanceTests/JetStream2
4. valgrind --tool=massif ../../WebKitBuild/Release/bin/jsc cli.js

OBSERVED RESULT

The attached file shows the log output of step 4.

EXPECTED RESULT

It should not crash.

SOFTWARE/OS VERSIONS

Linux: Ubuntu 18.04 running valgrind compiled on the machine from tip of master on the day of the bug report.

ADDITIONAL INFORMATION

20 core cpu with hyperthreading. last item of cpuinfo shows:

processor       : 39
vendor_id       : GenuineIntel
cpu family      : 6
model           : 85
model name      : Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz
stepping        : 4microcode       : 0x200005ecpu MHz         : 800.258cache size      : 14080 KBphysical id     : 1siblings        : 20core id         : 12cpu cores       : 10
apicid          : 57
initial apicid  : 57
fpu             : yes
fpu_exception   : yes
cpuid level     : 22
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd mba ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts pku ospke md_clear flush_l1d
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs
bogomips        : 4401.59
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:
Comment 1 Philippe Waroquiers 2019-08-15 12:33:47 UTC
Does the same also crash with other tools,
in particular, memcheck and none tools ?

Just to be sure, does it also crash if you specify --smc-check=all ?

In the attached log, we see that thread 1 is busy executing some code,
but thread 2 is blocked in a madvise syscall.
Remaining threads are in a timed wait call.

It is slightly strange to have thread 2 blocked in madvise syscall.
Maybe the application is doing very special actions on mapped pages ?

You could also see if adding --px-default=allregs-at-mem-access
or --px-default=allregs-at-each-insn  changes the behaviour.
(possibly, the javascript engine is changing protection of some pages,
and expect 'precise exception handling' for handling signals.
Comment 2 Paulo J. Matos 2019-08-15 12:50:47 UTC
Philippe, Thanks for your quick reply. Let me take a look at it soon and will get back to you.
Comment 3 Philippe Waroquiers 2019-09-06 04:22:08 UTC
Some feedback ?