Chromium e Chrome travando com muita frequência (Ubuntu 14.04)

Question

Então, algo estranho aconteceu esta semana. O Chrome e o Chromium começaram a congelar e subsequentemente falhar. Meu sistema continua funcionando bem, mas o Chrome e o Chromium congelam e depois fecham. A única coisa que eu acho que pode estar causando isso é o número de abas que eu abri (várias dúzias).

De qualquer forma, quando eu abri-los de volta, recebo a home page com a opção de restaurar. Eu clico em restaurar e tudo começa a carregar, então ele congela e trava de novo, e tudo se fecha. Portanto, não posso restaurar a sessão. (A propósito, existe uma maneira de obter uma lista dos sites que eu tinha aberto? Não consigo restaurar o cromo ou o cromo sem que eles falhem, então não consigo acessar nenhuma das minhas guias.)

Parece que esta pessoa está a ter problemas semelhantes: chrome com demasiada frequência no Ubuntu 14.04 . Eu tentei a solução proposta lá, mas não ajudou. Eu nem sei como depurar esse problema. Qualquer ajuda? Obrigado!

Chromium 37.0.2062.120 Ubuntu 14.04 e Google Chrome 38.0.2125.104

EDITAR

Eu corri do terminal e recebi esses erros. Tentarei a abordagem limits.conf com a reinicialização desta noite.

[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
[11401:11401:1028/111248:ERROR:browser_main_loop.cc(206)] /build/buildd/gtk+2.0-2.24.23/gdk/x11/gdkdrawable-x11.c:942 drawable is not a native X11 window (http://bugs.chromium.org/329991)
[11401:11438:1028/111248:ERROR:connection.cc(1060)] AppCache sqlite error 14, errno 0: unable to open database file, sql: SELECT cache_id, url, flags, response_id, response_size FROM Entries  WHERE url = ?
[11401:11438:1028/111248:ERROR:connection.cc(1060)] AppCache sqlite error 14, errno 0: unable to open database file, sql: SELECT cache_id, origin, type, namespace_url, target_url, is_pattern  FROM Namespaces WHERE origin = ?
[417:429:1028/111248:ERROR:webgraphicscontext3d_command_buffer_impl.cc(223)] CommandBufferProxy::Initialize failed.
[417:429:1028/111248:ERROR:webgraphicscontext3d_command_buffer_impl.cc(243)] Failed to initialize command buffer.
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.3tNbYP failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.4i6wXZ failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.ictTW9 failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.hnPgWj failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.xc3EVt failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.5ag4UD failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.YEluUN failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.PDiVTX failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.d48mT7 failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.3pYPSh failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.goJjSr failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.4ZrORB failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.4dHkRL failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.Fq7SQV failed: Too many open files
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.wT20R5 failed: Too many open files
[417:429:1028/111248:ERROR:webgraphicscontext3d_command_buffer_impl.cc(223)] CommandBufferProxy::Initialize failed.
[417:429:1028/111248:ERROR:webgraphicscontext3d_command_buffer_impl.cc(243)] Failed to initialize command buffer.
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.hcPdUf failed: Too many open files
[417:429:1028/111248:ERROR:webgraphicscontext3d_command_buffer_impl.cc(223)] CommandBufferProxy::Initialize failed.
[417:429:1028/111248:ERROR:webgraphicscontext3d_command_buffer_impl.cc(243)] Failed to initialize command buffer.
[11401:11441:1028/111248:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.com.google.Chrome.wuAOYp failed: Too many open files
[417:429:1028/111248:ERROR:webgraphicscontext3d_command_buffer_impl.cc(223)] CommandBufferProxy::Initialize failed.
[417:429:1028/111248:ERROR:webgraphicscontext3d_command_buffer_impl.cc(243)] Failed to initialize command buffer.
[11401:11401:1028/111248:ERROR:ipc_channel_posix.cc(213)] socketpair(): Too many open files
Aborted (core dumped)

    

Answer 1

O Chrome está falhando porque não pode abrir arquivos adicionais.

Você pode corrigir isso aumentando o número de possíveis arquivos abertos.

Atualize o /etc/security/limits.conf

* hard nofile 65535
* soft nofile 65535

e reinicializando.

    

Answer 2

Antes de atualizar limits.conf como sugerido por Thijs, tente se funciona para você. Em um shell, execute:

ulimit -a

Verifique a linha que lê open files (ou execute ulimit -n imediatamente). No meu sistema, o valor é 1024 . Saia do Chromium. Então, no mesmo terminal, questão

ulimit -n 4096
chromium-browser

Substitua 4096 por um valor adequado ao seu sistema. Você deve poder usar mais guias nesta sessão do navegador. Depois de encontrar um limite razoável, mantenha-o em limits.conf e reinicie.

Referências:

• link
• link
• link

Answer 3

Eu tive o mesmo problema. Após uma curta pesquisa no Google, encontro esta publicação que resolveu o meu problema. Talvez você deva tentar.