Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

升级 3.0 版后,原合法的博客帖子会导致 hexo serve 时卡死 #1148

Closed
victorwoo opened this issue Mar 26, 2015 · 8 comments
Closed

Comments

@victorwoo
Copy link

升级 3.0 版以后,原合法的博客帖子会导致运行 hexo serve 时卡死。
帖子内容仅仅包含一个代码块,代码块里有一个 GUID 字符串。

aaa

{8DEAF195-A06B-4B6F-99B2-11BEB6D6A0E3}

bbb

完整的 markdown 文件请在这里下载:
http://7xi9yc.com1.z0.glb.clouddn.com/2013-11-19-getting-mac-address-remotely.md

@gejiawen
Copy link

我也遇到过这种情况。可以使用{% raw %}{% endraw %}将那个字符串包裹起来。

@victorwoo
Copy link
Author

您是指在 markdown 中吗?
这应该属于 bug 吧。

@marvin-zhao
Copy link

一个非常长的单行代码段也导致无法正常generate
例如

Z2xvYmFsICRibG9nLCAkZGJfcHJlZml4LCAkbWJjb247DQokaG90dmlldz0kYmxvZy0+Z2V0Z3JvdXBieXF1ZXJ5KCJTRUxFQ1QgKiBGUk9NIGB7JGRiX3ByZWZpeH1ibG9nc2AgV0hFUkUgYHByb3BlcnR5YCA9MCBPUkRFUiBCWSBgdmlld3NgIERFU0MgTElNSVQgMCAsIHskbWJjb25bJ2VudHJ5bnVtJ119Iik7DQppZiAoaXNfYXJyYXkoJGhvdHZpZXcpKSB7DQokdmlld2hvd3M9Jzx1bD4nOw0KZm9yZWFjaCAoJGhvdHZpZXcgYXMgJG9uZWhvdHZpZXcpIHsNCiR2aWV3aG93cy49IjxsaT5beyRvbmVob3R2aWV3Wyd2aWV3cyddfV08YSBocmVmPVwicmVhZC5waHA/Ii4kb25laG90dmlld1snYmxvZ2lkJ10uIlwiPnskb25laG90dmlld1sndGl0bGUnXX08L2E+PC9saT4iOw0KfQ0KJHZpZXdob3dzLj0nPC91bD4nOw0KfSBlbHNlIHsNCiR2aWV3aG93cz0nTm8gdmlldyEnOw0KfQ0KJHBocHJldHVybj0kdmlld2hvd3M7

@victorwoo
Copy link
Author

而且 generate 碰到这种情况的时候会把系统内存资源耗尽。作者能否请查一下?
谢谢!

@Xuanwo
Copy link
Contributor

Xuanwo commented Apr 1, 2015

试试看包裹在

```plain
something
```

里面

@victorwoo
Copy link
Author

谢谢,不过2.x没有这个问题啊,能否作为 bug 查一查?

@victorwoo
Copy link
Author

谢谢,不过2.x没有这个问题啊,能否作为 bug 查一查?

Regards,
Victor

On Wed, Apr 1, 2015 at 6:45 PM, 漩涡 notifications@github.com wrote:

试试看包裹在

something

里面

—
Reply to this email directly or view it on GitHub
<https://github.com/hexojs/hexo/issues/1148#issuecomment-88437004>.

@leesei
Copy link
Member

leesei commented Jul 16, 2015

#1124

That is a issue with Highlight.js auto-detect, a feature added in 3.0

@leesei leesei closed this as completed Jul 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants