Closed Bug 106808 Opened 24 years ago Closed 24 years ago

Crash with apple.com (quicktime) in QUICKTIMEWEBHELPER.QTX

Categories

(Plugins Graveyard :: QuickTime (Apple), defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mgalli, Assigned: serhunt)

References

()

Details

(Keywords: crash, relnote, Whiteboard: [same stack in 4.x])

I am using Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.5+) Gecko/20011025 Go to http://www.apple.com Use the search field in the home page and submit. Then Mozilla crashes.
This works ok in the branch builds - win NT. Jaime, this is probably a trunk build crash as per the agent string pasted above.
The browser shuts down with no warning or errors on Win 2K: 1. Upon attempting to search from home page or 2. If I open the browser then paste in a string of search results that I generated through a different browser. Using rv:0.9.4 Gecko/20011019
Agreed, this sounds like a Mozilla trunk issue, as I have tried it on several different systems (NT and 98, with and without OuickTime), and have not been able to repro the problem.
btw - They are all using the 10.22 build.
BTW: With my latest mozilla: 1) if you URL the (search results) http://search.apple.com/s97is.vts?Action=FilterSearch&ResultTemplate=webx3.hts&ServerKey=Primary&collname=Apple&filter=nullflt.hts&SearchPage=http%3A%2F%2Fsearch.apple.com%2Findex.html&queryText=test&SEARCH.x=0&SEARCH.y=0 does not crash Then 2) if you go to home page (due to the quick time movie?) then type above URL, crash..
i stand corrected ... well, kinda i am using the 10.22 release, but the build id is 0.9.4 Gecko/20011019 I have only seen the problem on Susie's Win2K machine so far.
No stack trace?
Crashes before talkback.
Adding Roger 'Potter'. Roger, can you try this with linux?
HUnmnmm.. Was able to have a talkback report: ---------------------------------------------- Susie suggested http://www.quicktime.com. After loading this page (there is a quicktime in the page), we clicked one generic link in the bottom then crash: Incident ID: 37196028 Stack Trace QUICKTIMEWEBHELPER.QTX + 0x15c03 (0x62c95c03) QUICKTIMEWEBHELPER.QTX + 0x15b90 (0x62c95b90) 0x5b900003 0x03bc4e8b
Status: UNCONFIRMED → NEW
Ever confirmed: true
Additional note: the previous Mozilla crash happens when using Quicktime 4.1.2.
Jaime, it could be only with Quicktime older (like 4.1.2). IF this is true, do you think is a case for release notes?
Summary: Crash with apple.com (search option) → Crash with apple.com (quicktime)
how does this perform in Netscape 6.1? Is this a regression? cc'ing some MacHeads. Does anyone know what the install base of 4.1.2? hmmmmm ... I wonder if MSIE was crashing too, and that's why they had that upgrade to QuickTime 5 window. Defintely, a relnote ... defintely.
Keywords: crash, relnote
no quicktime for linux... no problems with linux mozilla. :(
->Plug-ins
Assignee: asa → av
Component: Browser-General → Plug-ins
QA Contact: doronr → shrir
Be sure you are using the latest version (5.0.2) of Quicktime from Apple: http://www.apple.com/quicktime/download/ This is important because this stack appears in talkback reports as far back as Nav 4.06: http://climate.mcom.com/reports/searchstacksignature.cfm?stacksig=QUICKTIMEWEBHELPER.QTX If this is still happening with the latest version of Quicktime, we need to contact Apple. Otherwise, I don't know if there is much we can do if plugin safety isn't catching the access violation.
Summary: Crash with apple.com (quicktime) → Crash with apple.com (quicktime) in QUICKTIMEWEBHELPER.QTX
Whiteboard: [same stack in 4.x]
OK. I thinking about moving to evangelism to see if we can sniff the browser before the crash (suggestion from Jaime). Thanks for the update Peter.
mgalli, does this still crash for you ? thx! wfm.
wfm 04/16 trnk
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Component: Plug-ins → QuickTime (Apple)
Product: Core → Plugins
QA Contact: shrir → apple-quicktime
Version: Trunk → unspecified
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.