You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 1124 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Keith Frost
Version: 3.04
OS: Windows 2000
Submission from: fb2.stratos.com (65.197.178.12)
Using the latest Ocaml 3.04 binary under Windows 2000, along with
ActiveState ActiveTcl 8.3.4.2, some short but random time after
beginning to use the Ocamlbrowser, I get a short error message indicating
that ocamlbrowser.exe tried to access memory (usually at 0x00000001) which
leads to a crash.
Does anybody else experience this?
Thanks,
Keith F.
The text was updated successfully, but these errors were encountered:
Full_Name: Keith Frost
Version: 3.04
OS: Windows 2000
Using the latest Ocaml 3.04 binary under Windows 2000, along with
ActiveState ActiveTcl 8.3.4.2, some short but random time after
beginning to use the Ocamlbrowser, I get a short error message indicating
that ocamlbrowser.exe tried to access memory (usually at 0x00000001) which
leads to a crash.
This has already been reported several times.
This unfortunate behaviour has been corrected in the CVS version,
and the next release should be ok. (We will check that everything
works next time!)
Original bug ID: 1124
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Keith Frost
Version: 3.04
OS: Windows 2000
Submission from: fb2.stratos.com (65.197.178.12)
Using the latest Ocaml 3.04 binary under Windows 2000, along with
ActiveState ActiveTcl 8.3.4.2, some short but random time after
beginning to use the Ocamlbrowser, I get a short error message indicating
that ocamlbrowser.exe tried to access memory (usually at 0x00000001) which
leads to a crash.
Does anybody else experience this?
Thanks,
Keith F.
The text was updated successfully, but these errors were encountered: