Closed
Bug 496200
Opened 15 years ago
Closed 15 years ago
browser crashes when attempting to play geotagged video
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 495333
People
(Reporter: michael.alstad, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.0.10) Gecko/2009042315 Firefox/3.0.10 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.0.10) Gecko/2009042315 Firefox/3.0.10 receive the following error message and browser crash when attempting to play geotagged video: A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script: http://maps.google.ca/maps/ms?client=firefox-a&oe=UTF-8&hl=en&channel=s&ie=UTF8&t=h&om=1&s=AARTsJocKZAspKa41PQeH9bIqy2rtnKlgw&msa=0&msid=105609701584765113301.00000111c23b969429817&ll=51.193115,-106.831055&spn=3.098503,5.987549&z=7&output=embed:4 Reproducible: Always Steps to Reproduce: 1.go to http://www.year01.com/pixelgrain/video.html 2.scroll down to map and click on blue or green icon to load video 3. Actual Results: browser chokes Expected Results: mapped video should play. I reported this error 7 days ago and as did not get a response so I sent a polite follow up message to see if my message was received. This was the response: "please note that sending mail again (which you apparently did) won't get better responses. I had starred this email and was waiting for some time when I was going to be friendly and suggest something. Instead... this is me frowning at you." https://bugzilla.mozilla.org/page.cgi?id=etiquette.html I was not aware of the so called "etiquette" guidelines. I am simply looking for an answer to a technical problem that only seems to be an issue with firefox. thanks. M
Comment 1•15 years ago
|
||
You can always write additional comments in your bug 495333, Michael.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•