Closed
Bug 75765
Opened 24 years ago
Closed 24 years ago
Crash on mouse over on default plugin
Categories
(Core Graveyard :: Plug-ins, defect)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: edburns, Assigned: serhunt)
References
()
Details
(Keywords: crash)
Platform: WinNT 4.0, Solaris 2.8
Browser: Trunk from 04/06/01, Netscape 6.01A on Solaris
Reproducible: Always
Steps to reproduce:
0. Make sure the only plugin you have installed is the null plugin.
0.5 Load some HTML page.
1. Load <http://www.g-wizz.net/ads/generic_popup_fosters.htm>.
2. Move the mouse over the puzzle piece icon. Go BACK using the back button
3. Go FORWARD using the forward button.
4. Move the mouse over the puzzle piece icon.
5. Repeat steps 2 thru 4 until crash.
Here's the console output.
Enabling Quirk StyleSheet
Enabling Quirk StyleSheet
nsLineLayout: ObjectFrame(object)(1)@0418261C didn't set max-element-size!
Document http://www.g-wizz.net/ads/generic_popup_fosters.htm loaded successfully
InstantiateEmbededPlugin for application/x-shockwave-flash
Inside nsPluginHostImpl::FindStoppedPluginForURL...
For * found plugin
D:\Projects\trunk\mozilla\dist\WIN32_D.OBJ\bin\plugins\npnul32.dll
Inside ns4xPluginInstance::Start(void)...
Inside ns4xPluginInstance::SetWindow(047FBB98)...
About to call CallNPP_SetWindowProc()...
Falling out of ns4xPluginInstance::SetWindow()...
created stream for http://www.g-wizz.net/ads/fosters_flash.swf
InstantiateEmbededPlugin.. returning
Inside ns4xPluginInstance::SetWindow(047FBB98)...
About to call CallNPP_SetWindowProc()...
Falling out of ns4xPluginInstance::SetWindow()...
Inside ns4xPluginInstance::SetWindow(047FBB98)...
About to call CallNPP_SetWindowProc()...
Falling out of ns4xPluginInstance::SetWindow()...
killing stream for http://www.g-wizz.net/ads/fosters_flash.swf
blank
WEBSHELL- = 3
/content/navigator.xul
/content/bookmarks/bookmarksPanel.xul
/ads/generic_popup_fosters.htm
Inside ns4xPluginInstance::SetWindow(00000000)...
ns4xPluginInstance::Stop()
ns4xPluginInstance::~ns4xPluginInstance()
WEBSHELL- = 2
WEBSHELL- = 1
WEBSHELL- = 0
Shut down app shell component {18c2f989-b09f-11d2-bcde-00805f0e1353},
rv=0x00000000
nsPluginHostImpl::Observe "xpcom-shutdown"
### beging nsCacheService::Shutdown()
### starting ~nsMemoryCacheDevice()
nsPluginHostImpl dtor
### nsCacheService is now destroyed.
CanUnload_enumerate: skipping native
Comment 3•24 years ago
|
||
edburns are you sure you got a crash?
the test html has
<body bgcolor="#002b5d"onLoad="setTimeout('window.close()',3000)"> in it.
try to open second window when you are testing, or disable javascript.
Comment 4•24 years ago
|
||
av, I think you can resolve this as invalid if there are no objections from
reporter.
I cannot reprodce it on Windows. If this is a platform specific please reopen.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 6•24 years ago
|
||
well, on today's windows build, the browser just closes when this page loads
(after 3-4 seconds). Not sure where this belongs(no talkback agent comes up) but
reopening.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 7•24 years ago
|
||
That is right, because as I've mentioned above this page has
<body bgcolor="#002b5d"onLoad="setTimeout('window.close()',3000)"> in it,
that means close the window after 3000 msec time out, if only one browser window
is opened on close it does normal termination of the process.
It's not a crash it's a NORMAL EXIT.
Comment 8•24 years ago
|
||
doh..thanks serge!
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → WORKSFORME
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•