Failed to save browser source

For technical support for all editions of CSE HTML Validator. Includes bug reports.

Failed to save browser source

Postby JWolters » Tue Jul 31, 2007 3:53 am

Using the integrated browser in Validator Pro for a secured website gives a warning 'Failed to save browser source to "{temp}\~cse_WBSource".' when browsing to a second page.

Refreshing the second page gives me the option to validate that page.

Browsing to another page crashes the application.

Entering the second and next URL's by hand is giving no warning or crashes.
JWolters
Rank 0 - Newcomer
Rank 0 - Newcomer
 
Posts: 4
Joined: Sun Dec 12, 2004 12:29 am

Postby Albert Wiersch » Tue Jul 31, 2007 2:34 pm

Hello,

Can you post exact steps and URLs to reproduce this issue? Also, what version of CSE HTML Validator are you using?
Image
Albert Wiersch
User avatar
Albert Wiersch
Site Admin
Site Admin
 
Posts: 2439
Joined: Sat Dec 11, 2004 10:23 am
Location: Near Dallas, TX

Postby JWolters » Wed Aug 01, 2007 2:21 am

I am using HTML Validator Pro 8.0403.

The URL's I am using are on our intranet and these are not available to the world. I checked another site which is running on intranet and internet and the error is only shown when using intranet.

This site is made using PatUser using HTTP authentication. I have made more sites using this library and they can be validated.

The steps I do are:
-goto the url http://jan.site.dmm (on our intranet)
-I need to login by HTTP authentication
-the first page is shown (with links to other pages)
-the first page can be validated (validating or not makes no difference for the error)
-click a link on the first page
-the error is shown
-refreshing the page removes the error and let's me validate the second page
-clicking a link on the seconde pages crashes HTML validator

- when I enter the links by hand there is no problem

I did a little check on the files in my temp folder and there are a lot of trb*.tmp files created on the same time as the ~cse_Websource file, about 2436 files when the error is shown.
JWolters
Rank 0 - Newcomer
Rank 0 - Newcomer
 
Posts: 4
Joined: Sun Dec 12, 2004 12:29 am

Postby Albert Wiersch » Wed Aug 01, 2007 10:47 am

Thanks for the details. I wish I could reproduce this as it would help. Unfortunately I'm not sure what's going on. I question all those temp files, especially the trb*.tmp files. I do not know where they are coming from.

It's possible that another program is interfering, but I don't know how or why (perhaps a security program).

When CSE HTML Validator crashes, does it offer to send a bug report? If so, then please send one and then let me know it has been sent via email or by replying here and I'll see if I can get any useful information from it.

If you can manage to reproduce this with publicly accessible pages, then that would help as well.
Image
Albert Wiersch
User avatar
Albert Wiersch
Site Admin
Site Admin
 
Posts: 2439
Joined: Sat Dec 11, 2004 10:23 am
Location: Near Dallas, TX

Postby JWolters » Fri Aug 03, 2007 2:49 am

I did send an email to support with a logfile from ProcesMon which shows that the tempfiles are generated by CSE80.exe.

HTMLValidator does not offer to send a bug-report.
JWolters
Rank 0 - Newcomer
Rank 0 - Newcomer
 
Posts: 4
Joined: Sun Dec 12, 2004 12:29 am

Postby Albert Wiersch » Fri Aug 03, 2007 1:41 pm

Hi Jan,

Thank you. I received the files and will be able to look at them next week.
Image
Albert Wiersch
User avatar
Albert Wiersch
Site Admin
Site Admin
 
Posts: 2439
Joined: Sat Dec 11, 2004 10:23 am
Location: Near Dallas, TX

Postby Albert Wiersch » Tue Aug 07, 2007 11:41 am

Hi Jan,

Thanks for the log file. I definitely see all the trb*.tmp files. I suspect that the browser engine component is generating these files but I don't know why. Could there be a JavaScript program in the page you are viewing in the browser that could be causing the creation of these files? You may want to try closing the web browser and see if the files are still created. I suspect they won't be.

So, I suspect that it is something in the document you are viewing in the browser that is causing the problem. I'm not sure if there is anything I can do about this. It would be easier to diagnose if I could reproduce the issue here.
Image
Albert Wiersch
User avatar
Albert Wiersch
Site Admin
Site Admin
 
Posts: 2439
Joined: Sat Dec 11, 2004 10:23 am
Location: Near Dallas, TX


Return to CSE Tech Support

Who is online

Users browsing this forum: Google [Bot] and 4 guests