New issue
Advanced search Search tips

Issue 671536 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2017
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Chromebook crashes often

Reported by kris...@gcompany.nl, Dec 6 2016

Issue description

Chrome Version       : 
Versie 54.0.2840.101 (64-bit)
Platform 8743.85.0 (Official Build) stable-channel lulu
Firmware Google_Lulu.6301.136.57

What steps will reproduce the problem?
(1) work with different profiles on Chromebook
(2) after a while it suddenly crashes
(3)

What is the expected result?
it shouldnt crash

What happens instead?
FOund the crash reports and got the message to create a bug. here is the log:
[1:1:1206/085624:VERBOSE1:zygote_main_linux.cc(619)] ZygoteMain: initializing 2 fork delegates
[23471:23471:1206/085624:VERBOSE1:drm_device_handle.cc(83)] Succeeded authenticating /dev/dri/card0 in 0 ms with 1 attempt(s)
[23501:23501:1206/085624:ERROR:interface_registry.cc(99)] Failed to locate a binder for interface: mojom::ResourceUsageReporter
[23501:23509:1206/085624:ERROR:drm_device_manager.cc(53)] Could not initialize DRM device for /sys/devices/platform/vgem/drm/card1
[23501:23509:1206/085625:VERBOSE1:drm_display.cc(102)] DRM configuring: device=/sys/devices/pci0000:00/0000:00:02.0/drm/card0 crtc=20 connector=29 origin=0,0 size=1920x1080
[1:1:1206/085639:ERROR:interface_registry.cc(99)] Failed to locate a binder for interface: mojom::ResourceUsageReporter
[1:21:1206/090041:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:13:1206/090049:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:13:1206/090049:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:13:1206/090049:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:13:1206/090049:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:13:1206/090049:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:13:1206/090049:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:13:1206/090049:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:13:1206/090049:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:13:1206/090049:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:13:1206/090049:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:13:1206/090049:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:13:1206/090049:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[1:49:1206/090114:WARNING:mediasession.cc(383)] Duplicate id found. Reassigning from 101 to 127
[1:49:1206/090200:WARNING:statscollector.cc(985)] The SSRC 996038872 is not associated with a receiving track
[1:49:1206/090211:WARNING:statscollector.cc(985)] The SSRC 1491799287 is not associated with a receiving track
[1:49:1206/090211:WARNING:statscollector.cc(985)] The SSRC 1491799287 is not associated with a receiving track
[1:1:1206/090216:ERROR:WebInputEventConversion.cpp(328)] NOTREACHED() hit.
[1:1:1206/090217:ERROR:WebInputEventConversion.cpp(328)] NOTREACHED() hit.
[1:49:1206/090256:WARNING:statscollector.cc(985)] The SSRC 1189442850 is not associated with a receiving track
[1:49:1206/090256:WARNING:statscollector.cc(985)] The SSRC 1189442850 is not associated with a receiving track
[1:49:1206/090256:WARNING:statscollector.cc(985)] The SSRC 1189442850 is not associated with a receiving track
[1:50:1206/090336:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 3 packets. Send time history too small?
[1:50:1206/090336:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 19 packets. Send time history too small?
[1:50:1206/090336:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 3 packets. Send time history too small?
[1:50:1206/090925:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 1 packet. Send time history too small?
[1:49:1206/091237:WARNING:statscollector.cc(985)] The SSRC 2865234332 is not associated with a receiving track
[1:50:1206/091404:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 2 packets. Send time history too small?
[1:50:1206/091404:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 4 packets. Send time history too small?
[1:50:1206/091404:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 3 packets. Send time history too small?
[1:50:1206/091404:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 7 packets. Send time history too small?
[1:50:1206/091404:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 4 packets. Send time history too small?
[1:50:1206/091404:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 3 packets. Send time history too small?
[1:50:1206/091404:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 1 packet. Send time history too small?
[1:50:1206/092233:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 1 packet. Send time history too small?
[1:50:1206/092853:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 9 packets. Send time history too small?
[1:50:1206/092853:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 8 packets. Send time history too small?
[1:50:1206/092853:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 6 packets. Send time history too small?
[1:50:1206/092853:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 8 packets. Send time history too small?
[1:50:1206/092853:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 9 packets. Send time history too small?
[1:50:1206/092853:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 4 packets. Send time history too small?
[1:50:1206/092853:WARNING:transport_feedback_adapter.cc(123)] Failed to lookup send time for 1 packet. Send time history too small?
[1:54:1206/093150:WARNING:rtp_packet_history.cc(132)] No match for getting seqNum 12809
[1:54:1206/093150:WARNING:rtp_packet_history.cc(132)] No match for getting seqNum 12810
[1:54:1206/093150:WARNING:rtp_packet_history.cc(132)] No match for getting seqNum 12811
[1:54:1206/093150:WARNING:rtp_packet_history.cc(132)] No match for getting seqNum 12812
[1:49:1206/093152:ERROR:rtpreceiver.cc(61)] AudioRtpReceiver::OnSetVolume: No audio channel exists.
[1:49:1206/093152:ERROR:rtpreceiver.cc(61)] AudioRtpReceiver::OnSetVolume: No audio channel exists.
[1:49:1206/093152:ERROR:rtpreceiver.cc(61)] AudioRtpReceiver::OnSetVolume: No audio channel exists.
[1:49:1206/093152:ERROR:rtpreceiver.cc(61)] AudioRtpReceiver::OnSetVolume: No audio channel exists.
[1:49:1206/093152:ERROR:rtpreceiver.cc(61)] AudioRtpReceiver::OnSetVolume: No audio channel exists.
[1:49:1206/093152:ERROR:rtpreceiver.cc(61)] AudioRtpReceiver::OnSetVolume: No audio channel exists.

Please provide any additional information below. Attach a screenshot if
possible.

 

Comment 1 by ajha@chromium.org, Dec 6 2016

Labels: M-54 OS-Chrome
Labels: Needs-Feedback
please provide a crash report id (from chrome://crashes)!

Comment 3 by kris...@gcompany.nl, Jan 27 2017

i am unable to retrieve crash IDs before 4/01
Project Member

Comment 4 by sheriffbot@chromium.org, Feb 3 2017

Labels: -Needs-Feedback Needs-Review
Owner: kathrelk...@chromium.org
Thank you for providing more feedback. Adding requester "kathrelkeld@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
In the absence of further data, this is likely a similar-sounding bug which has been addressed.  If you still see this crash and think you can provide more information, please file a new bug!

Sign in to add a comment