Bug in lazy-lock/font-lock

Hi, I am trying to use lazy-lock for fontification. I get the following error with the latest stable build of XEmacs on Windows XP. I have also tried it on Linux. Can someone suggest any solution to this ? /---- init.el | (require 'lazy-lock) | (add-hook 'font-lock-mode-hook 'turn-on-lazy-lock) \---- /---- custom.el | (custom-set-variables | '(font-menu-ignore-scaled-fonts nil) | '(font-lock-maximum-decoration t) | '(lazy-lock-minimum-size 50000) | '(lazy-lock-stealth-time nil) | '(font-lock-use-colors t) | '(lazy-lock-mode 1 nil (lazy-lock)) | '(font-lock-use-fonts nil) | '(font-lock-maximum-size nil)) \---- Sample backtrace: Signaling: (wrong-type-argument markerp nil) marker-position(nil) font-lock-fontify-syntactically-region(1 1220 nil) font-lock-default-fontify-region(1 1220 nil) font-lock-fontify-region(1 1220) byte-code("..." [end next beg text-property-any lazy-lock t 0 nil font-lock-fontify-region lazy-lock-put-text-property] 6) lazy-lock-fontify-region(1 1220) lazy-lock-fontify-window(#<window on "*Backtrace*" 0x1dd2>) walk-windows(lazy-lock-fontify-window no-minibuf #<mswindows-frame "emacs" 0x80b>) lazy-lock-maybe-fontify-frame(#<mswindows-frame "emacs" 0x80b>) byte-code("..." [starting-frame frame selected-frame frame-visible-p frame-minibuffer-only-p next-frame visible-nomini throw lazy-lock-frame-loop-done t lazy-lock-maybe-fontify-frame] 4) lazy-lock-pre-idle-fontify-windows() read-minibuffer-internal("Find file: ") byte-code("..." [standard-output standard-input prompt recursion-depth minibuffer-depth t read-minibuffer-internal] 2) read-from-minibuffer("Find file: " "~\\" #<keymap read-file-name-map size 2 0xcec> nil file-name-history nil nil) read-file-name-2(file-name-history "Find file: " nil nil nil nil read-file-name-internal) read-file-name-1(file file-name-history "Find file: " nil nil nil nil read-file-name-internal) read-file-name("Find file: " nil nil nil) call-interactively(find-file)