Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Flash/Shockwave Plugin Seems to Crash Browsers! Post 50075 by garfunkle on Thursday 15th of April 2004 11:15:14 PM
Old 04-16-2004
Flash/Shockwave Plugin Seems to Crash Browsers!

I have a problem, that's of course why I'm here. I just today installed, Vector Linux on a PII 233mhz with 160mb ram. The OS is stable, runs well, and is speedy for this older computer while running some GUI version. I can't recall which one. I can find out but it the browsers crash in all the GUI's. I've seem to have narrowed it down to Shockwave/Flash plugins. For some reason, the browsers crash when ever they come upon something flash or shockwave. A trip to candystand.com for example will kill it. Poor little dinosaur. I'm getting sick of having to revive this poor little guy. Anybody have any thoughts on this issue. The weird thing is, it crashed Freebird, Netscape 7, and Mozilla 1.6 all of them.

Any help would be cool.
 

6 More Discussions You Might Find Interesting

1. HP-UX

Mozilla & Macromedia Flash Player Plugin Problem

Hello All, I am using Mozilla 1.7.8 on hp-ux 11.00, and install flash player 6 for it. it is giving following errors and get crashed. when i want to open a site need flash plugin. Gtk-WARNING **: invalid cast from `GtkSuperWin' to `GtkWidget' Gtk-WARNING **: invalid cast from `GtkSuperWin'... (1 Reply)
Discussion started by: Awadhesh
1 Replies

2. UNIX for Dummies Questions & Answers

Flash causes 64-bit Ubuntu to crash

I've been running 64-bit Ubuntu for about 2 years now, but a few days ago it developed serious problems. Whenever I would load a Flash page* the computer would crash... well, sort of. The screen would go blank immediately, eventually causing the monitor to give the "no video detected" message. ... (0 Replies)
Discussion started by: CRGreathouse
0 Replies

3. Ubuntu

Flash causes 64-bit Ubuntu to crash

I've been running 64-bit Ubuntu for about 2 years now, but a few days ago it developed serious problems. Whenever I would load a Flash page* the computer would crash... well, sort of. The screen would go blank immediately, eventually causing the monitor to give the "no video detected" message. The... (2 Replies)
Discussion started by: CRGreathouse
2 Replies

4. OS X (Apple)

Flash player plugin on darwin for firefox

Hi, I have firefox beta 4 on my macbook with macports installed. How can the use adobe flash player plugin on darwin? Thanks (1 Reply)
Discussion started by: Stephan789
1 Replies

5. Solaris

How to make Adobe Flash Player plugin work for Firefox 13.01 on Solaris 11

How do I make Adobe flash Player work on solaris 11 for Firefox-13.0.1 which doesn't have a plugins directory? Thanks in advance.:o (0 Replies)
Discussion started by: Tenyhwa
0 Replies

6. Solaris

Looking for alternative to flash player plugin

I am looking for an alternative for adobe flash player plugin to solaris firefox browser since adobe no longer supports it in solaris. Could someone tell me if there is one. :o:wall: (2 Replies)
Discussion started by: Tenyhwa
2 Replies
SPEEDY(1p)																SPEEDY(1p)

NAME
speedy - a persistent Perl interpreter SYNOPSIS
speedy [ <perl options> ] [ -- <speedy options> ] [ <filename> ] DESCRIPTION
speedy, short for SpeedyCGI, is a way to run perl scripts persistently, which can make them run much more quickly. The most common way to make a script run persistently is by changing the interpreter line at the top of the script from: #!/usr/bin/perl to #!/usr/bin/speedy After the script is initially run, instead of exiting, the perl interpreter is kept running. During subsequent runs, this interpreter is used to handle new executions instead of starting a new perl interpreter each time. A very fast frontend program, written in C, is exe- cuted for each request. This fast frontend then contacts the persistent Perl process, which is usually already running, to do the work and return the results. Each perl script runs in its own Unix process, so one perl script can't interfere with another. Command line options can also be used to deal with programs that have memory leaks or other problems that might keep them from otherwise running persistently. Although SpeedyCGI is especially useful for CGI scripts, it can be used to keep any perl script running persistently. See CGI::Speedy- CGI(3.pm) for a complete description of SpeedyCGI, including further details on CGI execution and Apache issues. This manual page is based on that, but concentrates on running speedy from the command line. OPTIONS
The speedy command line is the same as for regular perl, with the exception that SpeedyCGI specific options can be passed in after a "--". For example the line: #!/usr/bin/speedy -w -- -t300 at the top of your script will set the perl option `-w' and will pass the `-t' option to SpeedyCGI, setting the Timeout value to 300 sec- onds. The options can also be set at run-time from the perl script using the CGI::SpeedyCGI module. OPTIONS AVAILABLE See CGI::SpeedyCGI(3.pm) for a complete description of the options. -p<string> BackendProg : Path to the speedy backend program. (Default: /usr/bin/speedy_backend) -B<number> BufsizGet : Use <number> bytes as the maximum size for the buffer that receives data from the perl backend. (Default: 131072) -b<number> BufsizPost : Use <number> bytes as the maximum size for the buffer that sends data to the perl backend. (Default: 131072) -g<string> Group : Allow a single perl interpreter to run multiple scripts. See CGI::SpeedyCGI(3.pm) for details. (Default: `none') -M<number> MaxBackends : If non-zero, limits the number of speedy backends running for this perl script to <number>. (Default: 0) -r<number> MaxRuns : Once the perl interpreter has run <number> times, re-exec the backend process. Zero indicates no maximum. This option is useful for processes that tend to consume resources over time. (Default: 500) -t<number> Timeout : If no new requests have been received after <number> seconds, exit the persistent perl interpreter. Zero indicates no timeout. (Default: 3600) -T<string> TmpBase : Use the given prefix for creating temporary files. This must be a filename prefix, not a directory name. (Default: `/tmp/speedy') -v Version : Print the SpeedyCGI version and exit. ENVIRONMENT
Environment variables can also be used to pass in options. This can only be done before the initial execution, not from within the script itself. The name of the environment variable is always SPEEDY_ followed by the option name in upper-case. For example to set the speedy Timeout option, use the environment variable named SPEEDY_TIMEOUT. FILES
/tmp/speedy* A unix socket used to connect to the backend process. See speedy_backend(1) for more information. AUTHOR
Sam Horrocks http://daemoninc.com sam@daemoninc.com NOTES
This manual page was created by Niko Tyni <ntyni@iki.fi> for Debian GNU/Linux, because the original program does not have one. It is based on the original and more complete CGI::SpeedyCGI(3pm) manual page. BUGS
There are command-line parsing incompatibilities with the real Perl. These aren't very easy to fix, as even the perlrun manpage isn't quite accurate on which parameters can be separated (like '-I') and which can't (like '-C'). speedy doesn't allow any of them to be sepa- rated. It considers the first option without a leading dash as the script filename. SEE ALSO
perl(1), CGI::SpeedyCGI(3pm), speedy_backend(1) SPEEDY(1p)
All times are GMT -4. The time now is 08:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy