Macroscope 1.7.5 automatically quits after crawl about seomacroscope HOT 12 CLOSED

URL List Processing -> Scan sites in URL List was unchecked and the List was came from both

from Clipboard and from a txt file

from seomacroscope.

@csaeum I'll also delete the comment that has your domain in it, as soon as things look good.

It looks like GitHub will keep that in the comment history otherwise.

from seomacroscope.

@csaeum this was the page (on the given domain) that caused a crash:

/bankettmoebel-bankettsuhl/bankettmoebel-stuhlwagen-tischwagen/transportwagen-tischwagen-rund.html

The keywords meta tag appears to be malformed. It has a comma that appears to be embedded into what would otherwise be considered a "keyword". It looks like somebody pasted a description into that field, instead of a keywords list.

In this type of situation, my code will be disregarding that type of problem, and register the keywords meta tag as being invalid.

from seomacroscope.

Thank you for reporting this @csaeum, that sounds like a crashing bug.

Do you have the URL that exhibits this behaviour please?

from seomacroscope.

I have fed it with a URL list but this is in a protected area because we are planning a relaunch of the page.

from seomacroscope.

OK that is understandable @csaeum, and thank you for the extra information, that helps to nail down where things might be going wrong.

However, I have not yet been able to reproduce the fault on this end.

Do you have any more information as to the exact steps to reproduce this fault please?

For example, did you use:

File -> Load URL List -> Load from Text File

...or:

File -> Load URL List -> Paste from Clipboard

And in Preferences, is:

URL List Processing -> Scan sites in URL List

...checked or unchecked?

Are there any other settings that you altered from the defaults for this task?

(I should probably add a simple method to save/load these Preferences settings...)

from seomacroscope.

The error still remains.

I had an URL scanned overnight and this morning the program was over

from seomacroscope.

Here Data von MS Errorlog:

Application Error

• 1000 2 100 0x80000000000000 156671 Application Papa-PC
• SEOMacroscopeSeriesOne.exe 1.7.5.0 5bf7a422 KERNELBASE.dll 6.1.7601.24291 5be785b6 e0434352 000000000000bded 10dc 01d49268bd2cecc4 C:\Program Files\SEO Macroscope\SEOMacroscopeSeriesOne.exe C:\Windows\system32\KERNELBASE.dll a21a9765-fe63-11e8-828a-5404a60f9227

.Net Runtime Error:

• 1026 2 0 0x80000000000000 156670 Application Papa-PC
• Anwendung: SEOMacroscopeSeriesOne.exe Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet. Ausnahmeinformationen: System.ArgumentException bei System.Text.RegularExpressions.RegexParser.ScanRegex() bei System.Text.RegularExpressions.RegexParser.Parse(System.String, System.Text.RegularExpressions.RegexOptions) bei System.Text.RegularExpressions.Regex..ctor(System.String, System.Text.RegularExpressions.RegexOptions, System.TimeSpan, Boolean) bei System.Text.RegularExpressions.Regex.IsMatch(System.String, System.String) bei SEOMacroscope.MacroscopeIntenseKeywordAnalysis.AnalyzeKeywordPresence(SEOMacroscope.MacroscopeDocument) bei SEOMacroscope.MacroscopeDocumentCollection.RecalculateStatsIntenseKeywordAnalysis(SEOMacroscope.MacroscopeDocument) bei SEOMacroscope.MacroscopeDocumentCollection.RecalculateDocCollectionFinal() bei SEOMacroscope.MacroscopeJobWorker+d__7.MoveNext() bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) bei System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() bei System.Threading.ThreadPoolWorkQueue.Dispatch()

hope that helps

from seomacroscope.

Many thanks for the excellent feedback @csaeum!

I think that that should be enough information for me to investigate this, and try to reproduce the fault.

It looks like it certainly is dying around the most recently added "RecalculateStatsIntenseKeywordAnalysis" functions.

I'll try and be conservative, but I'll carefully scan the domain that you gave me, and see if I can find out which page triggers the fault. Most likely, there is something about a particular page that my code doesn't properly account for, hence the unhandled exception.

from seomacroscope.

OK, that stack trace was perfect. It looks like I failed to check for null BodyText when analyzing keywords in the page's body text.

from seomacroscope.

Could you ever complete a new version so that I can test it?

I have the problem right now and so I'm stuck right now.

Although the URL's adapted you mean but still it is over here again and again.

How could I help you and me if the problem is solved?

from seomacroscope.

Hi @csaeum, this bug should be fixed in the v1.7.6 release now.

Many thanks for the feedback on this project @csaeum; I'm afraid it can take a while, as I don't always have much spare time to work on this.

from seomacroscope.