User Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:19.0) Gecko/19.0 Firefox/19.0 Build ID: 20121013030542 Steps to reproduce: On the demo, with media.peerconnection.enabled = true, when I click on “video” button, Firefox feeze and whole system (AMD Phenom II X4 945 / WinXP 64 / 8GB RAM). System is so slow that I'm forced to reboot.
(In reply to Célian VEYSSIÈRE from comment #0) > User Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:19.0) Gecko/19.0 > Firefox/19.0 > Build ID: 20121013030542 > > Steps to reproduce: > > On the demo, with media.peerconnection.enabled = true, when I click on > “video” button, Firefox feeze and whole system (AMD Phenom II X4 945 / WinXP > 64 / 8GB RAM). System is so slow that I'm forced to reboot. What camera are you using? Built-in or USB? What type of camera? Can you consistently reproduce this? I can't reproduce this on my Windows machine.
Logitec HD Webcam C720 (USB) Webcam software : Version 2.31 / Build 13.32.1044 I have not a second machine for reproduce this... I have only completely freeze my computer 2 times.
Oups, It's “Logitec HD Webcam C270”
A system freeze is a bug in code that runs with kernel mode privileges: the kernel or a driver. The worst thing that Firefox can do is to allocate all available memory but that's easy to check if you have the windows taskmanager already open.
Created attachment 671518 [details] memory It's strange, with last Nightly its work correctly. No lag, no freeze, but a lot of memory used.
After several tests, the memory usage increase takes place when I have this message "HARDWARE_UNAVAILABLE", when I have the video no problem.
OS: Windows Server 2003 → Windows XP
Hardware: x86_64 → All
Whiteboard: [getUserMedia] [blocking-gum-]
Marking this RESOLVED INCOMPLETE. Please re-open the bug if anyone can reproduce this issue.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [getUserMedia] [blocking-gum-] → [getUserMedia] [blocking-gum-][mozfr-community]
You need to log in before you can comment on or make changes to this bug.