 |
Home |
Download |
Getting Started |
Contact |
White Paper |
Examples |
Documentation |
Troubleshooting |
Newsgroup |
Mailing List |
Source Code |
Bugs |
Screenshots |
Filing bug reports
The preferred way to report a bug is using
bugzilla.
Click
here
to file a bug report on Protozilla.
Note: If you don't already have a bugzilla account at mozdev.org,
you will be prompted to create one when you submit the bug report.
Execution trace
Protozilla incorporates a verbose trace feature for debugging.
To enable tracing,
set the environment variable NSPR_LOG_MODULES to the value
"protozilla:5,protoCommon:5,nsIPCService:5,nsPipeChannel:5,nsPipeTransport:5"
before running mozilla from the command line.
You may also set the environment variable NSPR_LOG_FILE to a filename to capture the trace output, if you don't want it to appear on the console. If you report a bug, it would be very helpful if you could append the trace output to the bug report.
Latest bugs filed for protozilla
| Bug # | Description |
|---|---|
| 9965 | Fix 64-bit problems in IPC |
| 5460 | libipc.so points to undefines symbols (maybe the same as #2067) |
| 4992 | Non-privileged installation for Linux |
| 3937 | "Invalid ClassID or ContractID" in protozilla.js |
| 3511 | Support for notes:// protocol |
| 2672 | Progress indicator does not spin while waiting for process to return data |
| 2340 | OS X no functionality no feedback |
| 2067 | ipc.dll contains call to nonexistent function |
| 2006 | mozilla crashes if protozilla javascript-cgi outs long string |
| 1992 | protozilla presumes jar packaging |