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

Issue 710666 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Apr 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Aw Snap! due to mmap : chrome VmData 2149081088 exceed data ulimit 2147483647. Update limits or use boot option ignore_rlimit_data

Reported by rocketra...@gmail.com, Apr 11 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. Normal browsing with many tabs and two profiles open

What is the expected behavior?

What went wrong?
Eventually one or more tabs will Aw Snap! Looking at the dmesg it appears to be a memory allocation problem:

[302921.338478] mmap: chrome (7020): VmData 2149081088 exceed data ulimit 2147483647. Update limits or use boot option ignore_rlimit_data.
[302921.443437] traps: chrome[7020] trap invalid opcode ip:5595382fa571 sp:7fff5befe2d0 error:0
[302921.443448]  in chrome[5595353f2000+6aa5000]

I have not modified any ulimits to limit data memory -- all ulimits are at kernel defaults for Fedora except user nproc is 4096.:

# ulimit -a:
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 128374
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 4096
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 4096
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

Crashed report ID: e4cb385640000000

How much crashed? Just one tab

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Chrome version: 57.0.2987.133  Channel: stable
OS Version: 4.10.8-200.fc25.x86_64
Flash Version: 

The machine has 32 GB of RAM. Memory use:

              total        used        free      shared  buff/cache   available
Mem:            31G         16G        1.5G        8.8G         13G        5.0G
Swap:           19G         65M         19G

I have two gmail tabs open (in different profiles), according to the Chrome Inspector one of which is taking over 1G of memory and the other around 800 MB. Two Google Keep tabs (in different profiles) are taking about 450 MB each, and one Slack tab is taking about 625 MB. The rest of my tabs and extensions use less memory.
 
Labels: Needs-Triage-M57
Cc: ranjitkan@chromium.org
Labels: Needs-Feedback
From the stack trace it appears that issue is caused due to Out of memory. Request you to please try a system restart, relaunch chrome and try again. Please update us with your observations.

Stack Trace:
============
 CRASHED [SIGILL @ 0x00005595382fa571 ] MAGIC SIGNATURE THREAD
Stack Quality75%Show frame trust levels
0x00005595382fa571	(chrome -./out/Release/../../third_party/WebKit/Source/wtf/allocator/Partitions.cpp:137 )	WTF::partitionsOutOfMemoryUsing128M()
0x00005595382fa4c9	(chrome -./out/Release/../../third_party/WebKit/Source/wtf/allocator/Partitions.cpp:179 )	WTF::Partitions::handleOutOfMemory()
0x00005595376ba41e	(chrome -./out/Release/../../base/allocator/partition_allocator/partition_alloc.cc:266 )	base::partitionOutOfMemory(base::PartitionRootBase const*)
0x00005595376ba409	(chrome -./out/Release/../../base/allocator/partition_allocator/partition_alloc.cc:818 )	base::PartitionAllocSlowPath(base::PartitionRootBase*, int, unsigned long, base::PartitionBucket*)
0x00005595382fa28e	(chrome -./out/Release/../../base/allocator/partition_allocator/partition_alloc.h:673 )	WTF::PartitionAllocator::allocateBacking(unsigned long, char const*)
0x000055953943bde0	(chrome -./out/Release/../../third_party/WebKit/Source/wtf/allocator/PartitionAllocator.h:39 )	WTF::Deque<blink::WrapperMarkingData, 0ul, WTF::PartitionAllocator>::expandCapacity()
0x000055953943bcf4	(chrome -./out/Release/../../third_party/WebKit/Source/wtf/Deque.h:451 )	non-virtual thunk to blink::ScriptWrappableVisitor::pushToMarkingDeque(void (*)(blink::WrapperVisitor const*, void const*), blink::HeapObjectHeader* (*)(void const*), void (*)(), void const*) const
0x0000559539479054	(chrome -./out/Release/../../third_party/WebKit/Source/platform/heap/WrapperVisitor.h:171 )	blink::V8ANGLEInstancedArrays::traceWrappers(blink::WrapperVisitor*, blink::ScriptWrappable*)
0x000055953943b181	(chrome -./out/Release/../../third_party/WebKit/Source/bindings/core/v8/V8DOMWrapper.h:103 )	blink::V8DOMWrapper::associateObjectWithWrapper(v8::Isolate*, blink::ScriptWrappable*, blink::WrapperTypeInfo const*, v8::Local<v8::Object>)
0x000055953952e463	(chrome -./out/Release/../../third_party/WebKit/Source/bindings/core/v8/ToV8.h:40 )	blink::MutationRecordV8Internal::removedNodesAttributeGetterCallback(v8::FunctionCallbackInfo<v8::Value> const&)
0x00002672f2afe3aa		
0x0000267301a95fbd		
0x00002672f2305f14		
0x00002672f23a0622		
0x00002672f232db60		
0x0000559536561955	(chrome -./out/Release/../../v8/src/execution.cc:144 )	v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate*, bool, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*, v8::internal::Handle<v8::internal::Object>, v8::internal::Execution::MessageHandling)
0x00005595365616aa	(chrome -./out/Release/../../v8/src/execution.cc:180 )	v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*)
0x0000559536226217	(chrome -./out/Release/../../v8/src/api.cc:5098 )	v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*)
0x0000559539453f1b	(chrome -./out/Release/../../third_party/WebKit/Source/bindings/core/v8/V8ScriptRunner.cpp:650 )	blink::V8ScriptRunner::callFunction(v8::Local<v8::Function>, blink::ExecutionContext*, v8::Local<v8::Value>, int, v8::Local<v8::Value>*, v8::Isolate*)
0x000055953b141c46	(chrome -./out/Release/../../third_party/WebKit/Source/bindings/core/v8/V8MutationCallback.cpp:79 )	blink::V8MutationCallback::call(blink::HeapVector<blink::Member<blink::MutationRecord>, 0ul> const&, blink::MutationObserver*)
0x000055953977ddce	(chrome -./out/Release/../../third_party/WebKit/Source/core/dom/MutationObserver.cpp:271 )	blink::MutationObserver::deliver()
0x000055953977cf07	(chrome -./out/Release/../../third_party/WebKit/Source/core/dom/MutationObserver.cpp:308 )	blink::MutationObserver::deliverMutations()
0x00005595394339ba	(chrome -./out/Release/../../base/callback.h:85 )	blink::microtaskFunctionCallback(void*)
0x000055953664da09	(chrome -./out/Release/../../v8/src/isolate.cc:3407 )	v8::internal::Isolate::RunMicrotasksInternal()
0x000055953664e2e1	(chrome -./out/Release/../../v8/src/isolate.cc:3388 )	v8::internal::Isolate::RunMicrotasks()
0x0000559539453f69	(chrome -./out/Release/../../third_party/WebKit/Source/bindings/core/v8/V8ScriptRunner.cpp:657 )	blink::V8ScriptRunner::callFunction(v8::Local<v8::Function>, blink::ExecutionContext*, v8::Local<v8::Value>, int, v8::Local<v8::Value>*, v8::Isolate*)
0x000055953b13b8f1	(chrome -./out/Release/../../third_party/WebKit/Source/bindings/core/v8/ScheduledAction.cpp:135 )	blink::ScheduledAction::execute(blink::LocalFrame*)
0x000055953990dc4e	(chrome -./out/Release/../../third_party/WebKit/Source/core/frame/DOMTimer.cpp:170 )	blink::DOMTimer::fired()
0x0000559539368c2e	(chrome -./out/Release/../../third_party/WebKit/Source/platform/Timer.cpp:174 )	blink::TimerBase::runInternal()
0x00005595376bc85d	(chrome -./out/Release/../../base/callback.h:68 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x000055953937768b	(chrome -./out/Release/../../third_party/WebKit/Source/platform/scheduler/base/task_queue_manager.cc:377 )	blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue(blink::scheduler::internal::WorkQueue*, blink::scheduler::LazyNow, base::TimeTicks*)
0x0000559539376b15	(chrome -./out/Release/../../third_party/WebKit/Source/platform/scheduler/base/task_queue_manager.cc:245 )	blink::scheduler::TaskQueueManager::DoWork(base::TimeTicks, bool)
0x00005595376bc85d	(chrome -./out/Release/../../base/callback.h:68 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x000055953765370f	(chrome -./out/Release/../../base/message_loop/message_loop.cc:421 )	base::MessageLoop::RunTask(base::PendingTask*)
0x0000559537653204	(chrome -./out/Release/../../base/message_loop/message_loop.cc:430 )	base::MessageLoop::DoWork()
0x0000559537654d24	(chrome -./out/Release/../../base/message_loop/message_pump_default.cc:33 )	base::MessagePumpDefault::Run(base::MessagePump::Delegate*)
0x00005595376717af	(chrome -./out/Release/../../base/run_loop.cc:37 )	base::RunLoop::Run()
0x000055953a2bb290	(chrome -./out/Release/../../content/renderer/renderer_main.cc:200 )	content::RendererMain(content::MainFunctionParams const&)
0x00005595372d1d0b	(chrome -./out/Release/../../content/app/content_main_runner.cc:344 )	content::RunZygote(content::MainFunctionParams const&, content::ContentMainDelegate*)
0x00005595372d2e5b	(chrome -./out/Release/../../content/app/content_main_runner.cc:793 )	content::ContentMainRunnerImpl::Run()
0x00005595372d191d	(chrome -./out/Release/../../content/app/content_main.cc:20 )	content::ContentMain(content::ContentMainParams const&)
0x0000559535f37d00	(chrome -./out/Release/../../chrome/app/chrome_main.cc:112 )	ChromeMain
0x00007f4beb199400	(libc-2.24.so + 0x00020400 )	
0x0000559535f37c6f	(chrome + 0x00b45c6f )	SyscallAsm
0x0000559535f37b37	(chrome + 0x00b45b37 )	
0x00007f4bf1ad1b4a	(ld-2.24.so + 0x00010b4a )	
0x0000559535f37b37	(chrome + 0x00b45b37 )	
0x0000559535f37b60	(chrome + 0x00b45b60 )	_start
> From the stack trace it appears that issue is caused due to Out of memory. Request you to please try a system restart, relaunch chrome and try again. Please update us with your observations.

I think you missed the point of my issue. I know it was an OutOfMemoryException. What I was trying to explain is that my system has plenty of memory available: if you look at the results of `free` I posted, there are about 15GB of memory available. This happens often -- a system restart every time, especially when there are 15GB of memory available, is not an acceptable solution.
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 12 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Can you give these troubleshooting steps a try to see if they help:

1. In case you're using an antivirus or firewall software, ensure Chrome is trusted or permitted by these programs. You can also try temporarily disabling your antivirus or firewall to check whether this determines the issue.
2. Uninstall and reinstall Chrome again.
3. Clear all Cache and Cookies.
4. Your profile account might have been corrupted. Try creating a new browser user profile and check if it helps.
5. Run a scan with chrome clean up tool. This will help in removing the malicious software from the computer which tends to conflict with Chrome.
https://www.google.com/chrome/cleanup-tool/
6. Reset Chrome browser settings and check if it helps.

Thanks!
I have to wonder if you guys even read the description? You're sending debugging steps and tools for Windows, when this issue is for Linux.
Project Member

Comment 7 by sheriffbot@chromium.org, Apr 18 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 8 by sheriffbot@chromium.org, Apr 18 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment