Date: Thu, 31 Dec 2015 19:21:45 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 205584] www/qupzilla-qt5: Crashes after opening new tab Message-ID: <bug-205584-13-XFqk3ttmCH@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-205584-13@https.bugs.freebsd.org/bugzilla/> References: <bug-205584-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205584 --- Comment #5 from Arto Pekkanen <aksyom@gmail.com> --- (In reply to matthew from comment #4) I am using the FreeBSD-latest repository: http://pkg.freebsd.org/freebsd:10:x86:64/latest/ Repository build: https://pkg-status.freebsd.org/builds/default:default:101amd64:404493:beefy6 Browser crashes even with clean profile. Tried using the browser without speed dial on new tabs. Now I can open mult= iple tabs, and open pages in them via direct url or by using Google Search. However, I noticed another bug: some web pages cause the browser to freeze. Duckduckgo.com and Yahoo.com both cause a freeze. This also means that if I= use the location bar or start page to search, it will search via Duckduckgo.com= and freeze. When the browser freezes, it can be killed with SIGTERM. Google.com and Msn.com both work ... so the problem that causes the browser= to freeze is not only the speed dial, but also some specific combination of HT= ML and Javascript. I could not make a core dump of the browser after it freezes. Trying to use gdb's gcore command on the browser (after forcing break to gdb with SIGINT) causes gdb itself to freeze after it's virtual memory footprint (supposedly) reaches 34 GB. Also, when I try to use the browser inside a VNC Server session, it will not accept any keyboard input while other applications work just fine. PS. I provided a crash dump for the speed dial crash. Did you check it? It might provide useful clues on where this crash happens. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205584-13-XFqk3ttmCH>