Closed
Bug 1113135
Opened 10 years ago
Closed 3 years ago
[Ubuntu Firefox] Crash Bug in 34.0 "MessageChannel.cpp, line 1618" (a long domain name in /etc/hosts?)
Categories
(Core :: IPC, defect, P3)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: honey, Unassigned)
Details
(Keywords: crash)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0
Build ID: 20141127111021
Steps to reproduce:
Browsed the web
Actual results:
Browser crashed
Expected results:
Not crashed.
I don't know exactly waht the problem is, but I'm running firefox 34.0 from the Ubuntu repo's.
"[28120] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-34.0+build2/ipc/glue/MessageChannel.cpp, line 1618
[28120] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-34.0+build2/ipc/glue/MessageChannel.cpp, line 1618"
is what happens when it crashes.
The things open when it crashes (randomly):
Facebook, Youtube.
https://bugzilla.mozilla.org/show_bug.cgi?id=1072316 seems related, but it says 34.0 is not affected.
More updates to come(Want to submit ASAP before next crash)
Reporter | ||
Comment 1•10 years ago
|
||
OK, I think I've identified the problem.
If a very large string is in /etc/hosts, it will cause firefox to crash on a certain function.
I ran
perl -e 'print "127.0.0.1 ayylmao","x"x120000,".mit.edu"' >> /etc/hosts
restarted firefox, and started browsing, and it crashed.
Thanks
Comment 2•10 years ago
|
||
Can you try with a build from Mozilla? You can use a separate profile for it: http://kb.mozillazine.org/Category:Profiles
Severity: normal → critical
Component: Untriaged → IPC
Keywords: crash
Product: Firefox → Core
Summary: Crash Bug in 34.0 "MessageChannel.cpp, line 1618" → [Ubuntu Firefox] Crash Bug in 34.0 "MessageChannel.cpp, line 1618" (a long domain name in /etc/hosts?)
Updated•7 years ago
|
Priority: -- → P3
Comment 3•3 years ago
|
||
Closing this as resolved:inactive, this issue was not confirmed nor further info provided in 7 years.
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•